langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 03:55:25 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[PR #2007] fix: chat log wont show up #23371

New Issue
Closed
opened 2026-02-21 20:20:57 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:20:57 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/2007

State: closed
Merged: Yes

This bug was introduced by the upgrade to Next.

For reasons unknown, the chat/log/index.tsx component is executed twice, which also results in two instances of PromptLogModal being triggered.

When a user activates the onClick event in chat/log/index.tsx, the first PromptLogModal is successfully rendered. However, the second PromptLogModal inadvertently triggers the onCancel of the first modal through the

useClickAway(() => {
    if (mounted)
      onCancel()
  }, ref)

Consequently, the entire PromptLogModal is prematurely dismissed.

The current solution involves stopping the event propagation in chat/log/index.tsx to prevent the double triggering of PromptLogModal. This approach is both controlled and effectively resolves the issue.

**Original Pull Request:** https://github.com/langgenius/dify/pull/2007 **State:** closed **Merged:** Yes --- This bug was introduced by the upgrade to `Next`. For reasons unknown, the `chat/log/index.tsx` component is executed twice, which also results in two instances of `PromptLogModal` being triggered. When a user activates the `onClick` event in `chat/log/index.tsx`, the first `PromptLogModal` is successfully rendered. However, the second `PromptLogModal` inadvertently triggers the `onCancel` of the first modal through the ``` useClickAway(() => { if (mounted) onCancel() }, ref) ``` Consequently, the entire `PromptLogModal` is prematurely dismissed. The current solution involves stopping the event propagation in `chat/log/index.tsx` to prevent the double triggering of `PromptLogModal`. This approach is both controlled and effectively resolves the issue.
yindo added the pull-request label 2026-02-21 20:20:57 -05:00
yindo closed this issue 2026-02-21 20:20:57 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#23371
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?