Skip to content

encoder: ensure that flush is finished #327

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

Merged
merged 1 commit into from
Feb 27, 2025

Conversation

surban
Copy link
Contributor

@surban surban commented Feb 27, 2025

Once a flush has been started some encoders (for example xz2) require that the flush is completed before writing more data.

Once a flush has been started some encoders
(for example xz2) require that the flush is completed
before writing more data.
Copy link
Collaborator

@NobodyXu NobodyXu left a comment

Choose a reason for hiding this comment

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

Thank you for fixing the bug!

@NobodyXu NobodyXu added this pull request to the merge queue Feb 27, 2025
Merged via the queue into Nullus157:main with commit e67aba9 Feb 27, 2025
16 checks passed
Copy link

codecov bot commented Feb 27, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 0.00%. Comparing base (04141de) to head (c6d9531).
Report is 14 commits behind head on main.

Additional details and impacted files
@@     Coverage Diff     @@
##   main   #327   +/-   ##
===========================
===========================

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@link2xt
Copy link
Contributor

link2xt commented Mar 14, 2025

There is very similar code in futures implementation, it should be kept in sync.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants