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 #28218] fix: click log panel of log page cause whole page crash #31984

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

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

State: closed
Merged: Yes

Important

  1. Make sure you have read our contribution guidelines
  2. Ensure there is an associated issue and you have been assigned to it
  3. Use the correct syntax to link this PR: Fixes #<issue number>.

Summary

fix https://github.com/langgenius/dify/issues/28211

because now we imports StatusPanel, WorkflowRunningStatus, and—most importantly—useStore from ../store.
It reads isListening so the modal can auto-switch to the detail tab and show the live “running” panel when a workflow is streaming

error log:

Error Type
Runtime Error

Error Message
Missing WorkflowContext.Provider in the tree

at useStore (app/components/workflow/store/workflow/index.ts:90:11)
at RunPanel (app/components/workflow/run/index.tsx:40:31)
at MessageLogModal (app/components/base/message-log-modal/index.tsx:64:7)
at DetailPanel (app/components/app/log/list.tsx:782:9)
at ChatConversationDetailComp (app/components/app/log/list.tsx:888:10)
at ConversationList (app/components/app/log/list.tsx:1107:15)
at Logs (app/components/app/log/index.tsx:81:15)
at LogAnnotation (app/components/app/log-annotation/index.tsx:57:83)
at Logs (app/(commonLayout)/app/(appDetailLayout)/[appId]/logs/page.tsx:7:5)
Code Frame
88 | const store = useContext(WorkflowContext)
89 | if (!store)

90 | throw new Error('Missing WorkflowContext.Provider in the tree')
| ^
91 |
92 | return useZustandStore(store, selector)
93 | }

Next.js version: 15.5.6 (Turbopack)

Screenshots

image
Before After
... ...

Checklist

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
**Original Pull Request:** https://github.com/langgenius/dify/pull/28218 **State:** closed **Merged:** Yes --- > [!IMPORTANT] > > 1. Make sure you have read our [contribution guidelines](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) > 1. Ensure there is an associated issue and you have been assigned to it > 1. Use the correct syntax to link this PR: `Fixes #<issue number>`. ## Summary <!-- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. --> fix https://github.com/langgenius/dify/issues/28211 because now we imports StatusPanel, WorkflowRunningStatus, and—most importantly—[useStore from ../store](https://github.com/langgenius/dify/blob/1e6d0de48bbc08b069f721fd615b18ed277b695b/web/app/components/workflow/run/index.tsx#L17). It reads isListening so the modal can auto-switch to the detail tab and show the live “running” panel when a workflow is streaming error log: ``` Error Type Runtime Error Error Message Missing WorkflowContext.Provider in the tree at useStore (app/components/workflow/store/workflow/index.ts:90:11) at RunPanel (app/components/workflow/run/index.tsx:40:31) at MessageLogModal (app/components/base/message-log-modal/index.tsx:64:7) at DetailPanel (app/components/app/log/list.tsx:782:9) at ChatConversationDetailComp (app/components/app/log/list.tsx:888:10) at ConversationList (app/components/app/log/list.tsx:1107:15) at Logs (app/components/app/log/index.tsx:81:15) at LogAnnotation (app/components/app/log-annotation/index.tsx:57:83) at Logs (app/(commonLayout)/app/(appDetailLayout)/[appId]/logs/page.tsx:7:5) Code Frame 88 | const store = useContext(WorkflowContext) 89 | if (!store) 90 | throw new Error('Missing WorkflowContext.Provider in the tree') | ^ 91 | 92 | return useZustandStore(store, selector) 93 | } Next.js version: 15.5.6 (Turbopack) ``` ## Screenshots <img width="1044" height="767" alt="image" src="https://github.com/user-attachments/assets/6119755f-ce52-45c8-9bdd-4c9250f90894" /> | Before | After | |--------|-------| | ... | ... | ## Checklist - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [x] I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!) - [x] I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change. - [x] I've updated the documentation accordingly. - [x] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods
yindo added the pull-request label 2026-02-21 20:50:31 -05:00
yindo closed this issue 2026-02-21 20:50:31 -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#31984
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?