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

main-ci can't run properly #20401

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

Originally created by @longbingljw on GitHub (Nov 19, 2025).

Originally assigned to: @JohnJyong on GitHub.

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.10.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

when contributing,trigger ci,push or pull request

✔️ Expected Behavior

main-ci can run properly

❌ Actual Behavior

main-ci can't run properly
error parsing called workflow
".github/workflows/main-ci.yml"
-> "./.github/workflows/vdb-tests.yml"
workflow is not reusable as it is missing a on.workflow_call trigger
Originally created by @longbingljw on GitHub (Nov 19, 2025). Originally assigned to: @JohnJyong on GitHub. ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.10.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce when contributing,trigger ci,push or pull request ### ✔️ Expected Behavior main-ci can run properly ### ❌ Actual Behavior main-ci can't run properly error parsing called workflow ".github/workflows/main-ci.yml" -> "./.github/workflows/vdb-tests.yml" : workflow is not reusable as it is missing a `on.workflow_call` trigger
yindo added the 🌚 invalid label 2026-02-21 20:07:16 -05:00
yindo closed this issue 2026-02-21 20:07:16 -05:00
yindo commented 2026-02-21 20:07:16 -05:00
Author
Owner
Copy Link
Copy Source

@longbingljw commented on GitHub (Nov 19, 2025):

https://github.com/langgenius/dify/pull/28336.In this pr,the bro modified vdb-tests.yml but forgot to remove the call to it from main-ci.yml

@longbingljw commented on GitHub (Nov 19, 2025): https://github.com/langgenius/dify/pull/28336.In this pr,the bro modified vdb-tests.yml but forgot to remove the call to it from main-ci.yml
yindo commented 2026-02-21 20:07:17 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 19, 2025):

You're right—if main-ci.yml still calls vdb-tests.yml after that workflow was modified (or removed), the CI pipeline will fail because it tries to run a job that no longer matches the expected structure or doesn't exist. To fix this, the reference to vdb-tests.yml in main-ci.yml should be removed or updated in sync with changes to the workflow file. This will prevent CI failures and keep the pipeline stable source.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Nov 19, 2025): <!-- Answer --> You're right—if main-ci.yml still calls vdb-tests.yml after that workflow was modified (or removed), the CI pipeline will fail because it tries to run a job that no longer matches the expected structure or doesn't exist. To fix this, the reference to vdb-tests.yml in main-ci.yml should be removed or updated in sync with changes to the workflow file. This will prevent CI failures and keep the pipeline stable [source](https://github.com/langgenius/dify/blob/88c9b18cb679cc037be68ac5f168c6bc28809889/.github/workflows/main-ci.yml#L27-L72). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/73b177f5-af0b-4a1d-82f6-331dbcdde2e1?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/73b177f5-af0b-4a1d-82f6-331dbcdde2e1?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/73b177f5-af0b-4a1d-82f6-331dbcdde2e1?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/73b177f5-af0b-4a1d-82f6-331dbcdde2e1?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/73b177f5-af0b-4a1d-82f6-331dbcdde2e1?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/73b177f5-af0b-4a1d-82f6-331dbcdde2e1?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/73b177f5-af0b-4a1d-82f6-331dbcdde2e1?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/28381)
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 🌚 invalid
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#20401
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?