-
Notifications
You must be signed in to change notification settings - Fork 14
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 slicer upload in some cases #486
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lol. Does it mean that RC10 isn't perfect again in term of Slicer
? How did you find it?
Commit's body does not end with a period.
The period is fixed. I'm updating our gates. Inside HTTP one I updated all upload places to slicer using. RC10 is not perfect, but much closer to it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's disappointing to see this given that exactly this issue had been discussed numerous times in slicer-related PRs. Yet at the same all PRs were reviewed successfully before the respective merges.
Let's hope the new test won't let it happen again.
53cdd80
to
8adfec8
Compare
25d1ad3
to
1775115
Compare
The case when the reader returns io.EOF with the last data chunk. Slicer was closing the writer without payload writing. Signed-off-by: Evgenii Baidakov <evgenii@nspcc.io>
The case when the reader returns io.EOF with the last data chunk. Slicer was closing the writer without payload writing