-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Ensure zero byte files can be sent #5125
Conversation
67ab952
to
8843964
Compare
Codecov Report
@@ Coverage Diff @@
## master #5125 +/- ##
==========================================
+ Coverage 97.50% 97.54% +0.03%
==========================================
Files 43 43
Lines 8824 8825 +1
Branches 1415 1416 +1
==========================================
+ Hits 8604 8608 +4
+ Misses 103 102 -1
+ Partials 117 115 -2
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
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.
LGTM, Thanks!
💚 Backport successfulThe PR was backported to the following branches:
|
Backports the following commits to 3.7: - Ensure zero byte files can be sent (#5125) Co-authored-by: J. Nick Koston <[email protected]>
What do these changes do?
Restores previous behavior of not throwing an exception when sending a zero byte file.
Are there changes in behavior for the user?
Regression fix
Related issue number
Fixes #5124
Checklist
CONTRIBUTORS.txt
CHANGES
folder<issue_id>.<type>
for example (588.bugfix)issue_id
change it to the pr id after creating the pr.feature
: Signifying a new feature..bugfix
: Signifying a bug fix..doc
: Signifying a documentation improvement..removal
: Signifying a deprecation or removal of public API..misc
: A ticket has been closed, but it is not of interest to users.