Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: raise error on import of AsyncPipeline #178

Merged
merged 3 commits into from
Jan 27, 2025

Conversation

Amnah199
Copy link
Contributor

@Amnah199 Amnah199 commented Jan 27, 2025

Related Issues

  • fixes: New release will not support AsyncPipeline due to updates in pipeline run logic

Proposed Changes:

  • Raise an RuntimeError when the user tries to initialize async pipelines in 0.5.0 release.
  • Remove all tests related to async pipelines.

How did you test it?

Ran code manually

Notes for the reviewer

Checklist

@coveralls
Copy link

coveralls commented Jan 27, 2025

Pull Request Test Coverage Report for Build 12990000451

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 45 unchanged lines in 4 files lost coverage.
  • Overall coverage decreased (-0.6%) to 63.774%

Files with Coverage Reduction New Missed Lines %
core/pipeline/async_pipeline.py 1 66.67%
components/retrievers/in_memory/init.py 3 0.0%
components/retrievers/in_memory/bm25_retriever.py 20 0.0%
components/retrievers/in_memory/embedding_retriever.py 21 0.0%
Totals Coverage Status
Change from base Build 12988006707: -0.6%
Covered Lines: 1345
Relevant Lines: 2109

💛 - Coveralls

@Amnah199 Amnah199 marked this pull request as ready for review January 27, 2025 13:23
@Amnah199 Amnah199 requested review from a team as code owners January 27, 2025 13:23
@Amnah199 Amnah199 requested review from dfokina, mpangrazzi, julian-risch and davidsbatista and removed request for a team, dfokina and mpangrazzi January 27, 2025 13:23
Copy link
Member

@julian-risch julian-risch left a comment

Choose a reason for hiding this comment

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

LGTM! 👍 For now, we'll need to pause the experiment on AsyncPipeline. As a next step, we should add a comment to the GitHub discussion about the experimental AsyncPipeline, explain that the experiment is paused, and point to 0.4.0 release. #152
Similarly, we should add a note to the cookbook or remove it entirely: https://github.com/deepset-ai/haystack-cookbook/blob/bd82aac09307379fa082e374d8855769a943b9e7/notebooks/async_pipeline.ipynb

Copy link
Contributor

@davidsbatista davidsbatista left a comment

Choose a reason for hiding this comment

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

LGTM - looks good to me - imported the async gave me the expected error, and I was also able to run a pipeline with the new logic.

@Amnah199 Amnah199 merged commit cbbf088 into main Jan 27, 2025
15 checks passed
@Amnah199 Amnah199 deleted the raise-error-for-async-pipeline branch January 27, 2025 13:44
mathislucka pushed a commit that referenced this pull request Jan 28, 2025
* raise error for async import
* Remove all async pipeline tests
mathislucka pushed a commit that referenced this pull request Jan 31, 2025
* raise error for async import
* Remove all async pipeline tests

(cherry picked from commit cbbf088)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants