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

[PR #8558] Enhance Readme Documentation to Clarify the Importance of Celery Service #26093

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

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

State: closed
Merged: Yes

Key Improvements:

Clearly state the necessity of the Celery service and its role in task scheduling. Provide clear startup guidelines and configuration suggestions to help users avoid common configuration errors. We believe these enhancements will greatly improve the readability and practicality of the documentation, ensuring that users can smoothly start and utilize the Celery service.

Associated Issues:

Checklist:

Important

Please review the checklist below before submitting your pull request.

  • Please open an issue before creating a PR or link to an existing issue
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods

Description

Upon reviewing user feedback, we've identified that certain statements in the Readme documentation might be misleading, causing many users to fail in properly initiating the Celery application. This not only impacts the efficiency of task execution but can also lead to prolonged task blocking. To address this issue, we have revised the relevant prompts in the Readme documentation to ensure that users fully comprehend the significance of the Celery service and can configure and launch it correctly.

Fixes

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update, included: Dify Document
  • Improvement, including but not limited to code refactoring, performance optimization, and UI/UX improvement
  • Dependency upgrade
**Original Pull Request:** https://github.com/langgenius/dify/pull/8558 **State:** closed **Merged:** Yes --- Key Improvements: Clearly state the necessity of the Celery service and its role in task scheduling. Provide clear startup guidelines and configuration suggestions to help users avoid common configuration errors. We believe these enhancements will greatly improve the readability and practicality of the documentation, ensuring that users can smoothly start and utilize the Celery service. Associated Issues: - https://github.com/langgenius/dify/issues?q=%E6%8E%92%E9%98%9F%E4%B8%AD - https://github.com/langgenius/dify/issues?q=Queuing # Checklist: > [!IMPORTANT] > Please review the checklist below before submitting your pull request. - [X] Please open an issue before creating a PR or link to an existing issue - [X] I have performed a self-review of my own code - [X] I have commented my code, particularly in hard-to-understand areas - [X] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods # Description Upon reviewing user feedback, we've identified that certain statements in the Readme documentation might be misleading, causing many users to fail in properly initiating the Celery application. This not only impacts the efficiency of task execution but can also lead to prolonged task blocking. To address this issue, we have revised the relevant prompts in the Readme documentation to ensure that users fully comprehend the significance of the Celery service and can configure and launch it correctly. Fixes ## Type of Change - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [X] Improvement, including but not limited to code refactoring, performance optimization, and UI/UX improvement - [ ] Dependency upgrade
yindo added the pull-request label 2026-02-21 20:35:05 -05:00
yindo closed this issue 2026-02-21 20:35:06 -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#26093
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?