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

[PR #2778] debug/chat: increase notify error duration to 3000 #23831

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

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

State: closed
Merged: Yes

Description

This PR increases the notification error duration in the debug/chat component from the default to 3000 milliseconds. This change aims to improve user experience by ensuring error messages are visible for a sufficient amount of time, allowing users to better understand and react to them. No new dependencies are introduced with this change.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Testing should verify that the increased duration does not negatively impact user experience or interfere with other notifications. Test cases include:

  • Manual testing to ensure error notifications now persist for 3000 milliseconds.
  • Automated tests to verify no side effects on notification system behavior.

Suggested Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • My changes generate no new warnings
**Original Pull Request:** https://github.com/langgenius/dify/pull/2778 **State:** closed **Merged:** Yes --- # Description This PR increases the notification error duration in the debug/chat component from the default to 3000 milliseconds. This change aims to improve user experience by ensuring error messages are visible for a sufficient amount of time, allowing users to better understand and react to them. No new dependencies are introduced with this change. ## Type of Change - [x] Bug fix (non-breaking change which fixes an issue) # How Has This Been Tested? Testing should verify that the increased duration does not negatively impact user experience or interfere with other notifications. Test cases include: - [x] Manual testing to ensure error notifications now persist for 3000 milliseconds. - [ ] Automated tests to verify no side effects on notification system behavior. # Suggested Checklist: - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] My changes generate no new warnings
yindo added the pull-request label 2026-02-21 20:21:50 -05:00
yindo closed this issue 2026-02-21 20:21:50 -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#23831
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?