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

[PR #25183] fix: Ensure the order of execution steps are correct when logging with Weave by W&B #30958

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

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

State: closed
Merged: Yes

fixes #25182

Summary

This very short PR fixes the issue of workflow steps showing up out of order on Weave by W&B dashboard. Also, updates the default tag passed with the traces.

Screenshots

Before After
Screenshot 2025-09-04 at 23 21 19 image

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/25183 **State:** closed **Merged:** Yes --- fixes #25182 ## Summary This very short PR fixes the issue of workflow steps showing up out of order on Weave by W&B dashboard. Also, updates the default tag passed with the traces. ## Screenshots | Before | After | |--------|-------| | <img width="auto" height="400" alt="Screenshot 2025-09-04 at 23 21 19" src="https://github.com/user-attachments/assets/f0e9b658-34d9-4ce4-8f3a-63d9fb695dc3" /> | <img width="auto" height="400" alt="image" src="https://github.com/user-attachments/assets/49a3075a-02b6-47b9-8d06-dc3517763e4c" /> | ## 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. - [] 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:48:33 -05:00
yindo closed this issue 2026-02-21 20:48:33 -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#30958
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?