Skip to content

Conversation

@fatelei
Copy link
Contributor

@fatelei fatelei commented Dec 28, 2025

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 #30225

allow fail fast, not wait all

Screenshots

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

@dosubot dosubot bot added size:L This PR changes 100-499 lines, ignoring generated files. 👻 feat:rag Embedding related issue, like qdrant, weaviate, milvus, vector database. labels Dec 28, 2025
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @fatelei, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the system's resilience and responsiveness by introducing a 'fail-fast' strategy for concurrent retrieval operations. Instead of waiting for all parallel tasks to finish, the system will now immediately halt and report an error if any individual task fails. This prevents unnecessary resource consumption and provides quicker feedback in case of issues during data retrieval.

Highlights

  • Fail-Fast Mechanism for Concurrent Operations: Implemented a 'fail-fast' approach for concurrent tasks, ensuring that if any task encounters an exception, remaining tasks are immediately cancelled, and the error is propagated without waiting for all tasks to complete.
  • Concurrent Futures Update: Modified retrieval_service.py to switch from concurrent.futures.wait(..., return_when=ALL_COMPLETED) to iterating through concurrent.futures.as_completed, allowing for early detection of exceptions and cancellation of outstanding futures.
  • Thread-Based Cancellation and Exception Handling: Introduced threading.Event and a shared exception list in dataset_retrieval.py to manage cancellation signals and collect exceptions across multiple worker threads, enabling fail-fast behavior for thread-based operations.
  • Test Suite Alignment: Updated unit tests to mock concurrent.futures.as_completed to accurately reflect the new fail-fast behavior in the retrieval_service module.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces fail-fast behavior for concurrent retrieval tasks, which is a great improvement for efficiency and error handling. When one task fails, it attempts to cancel the others and stop waiting. I've reviewed the changes and found a critical issue in retrieval_service.py where the fail-fast condition is incorrect and will never trigger. Additionally, I've identified a couple of places in dataset_retrieval.py where the implementation could be improved to make the fail-fast behavior more responsive. My detailed comments provide suggestions for these points.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

👻 feat:rag Embedding related issue, like qdrant, weaviate, milvus, vector database. lgtm This PR has been approved by a maintainer size:L This PR changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Knowledge base retrieval may unexpectedly take a significant amount of time.

3 participants