-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Better handling of DB timeouts on long downloads #36978
Conversation
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
Codecov Report
@@ Coverage Diff @@
## master #36978 +/- ##
============================================
- Coverage 64.75% 64.28% -0.47%
- Complexity 19138 19139 +1
============================================
Files 1270 1270
Lines 74912 74879 -33
Branches 1329 1329
============================================
- Hits 48507 48134 -373
- Misses 26014 26354 +340
Partials 391 391
Continue to review full report at Codecov.
|
I can't increase the coverage. The cache can't be mocked, so we can't force the DriverException to trigger |
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 💃
Description
Try to avoid hitting the DB after a long download, which could cause a failure if the DB connection timed out
Related Issue
https://github.com/owncloud/enterprise/issues/3538
Motivation and Context
How Has This Been Tested?
Checked after setting a 10 sec DB timeout and then downloading a big file through a slow network.
The first time, we still need to hit the DB to update the checksum (currently we're logging a message and keep working), but once the checksum is there, there won't be any error.
Screenshots (if appropriate):
Types of changes
Checklist: