-
Notifications
You must be signed in to change notification settings - Fork 807
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
do not check every 5 seconds files with infinite timeout (= 0) #6059
do not check every 5 seconds files with infinite timeout (= 0) #6059
Conversation
we want to schedule a new sync attempt if a file is likely to have been unlocked due to timeout expiring on server but if the timeout is null (equal to 0), there will be no timeout on server and no automated unlocking, so do not schedule a sync every 5 seconds to check for it Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
1922371
to
a17b360
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #6059 +/- ##
==========================================
- Coverage 60.28% 60.24% -0.05%
==========================================
Files 145 145
Lines 18866 18868 +2
==========================================
- Hits 11374 11367 -7
- Misses 7492 7501 +9
|
Kudos, SonarCloud Quality Gate passed! |
/backport to stable-3.10 |
/backport to stable-3.9 |
AppImage file: nextcloud-PR-6059-a17b3608d93f503114880d4880584dcd0feee14f-x86_64.AppImage |
we want to schedule a new sync attempt if a file is likely to have been unlocked due to timeout expiring on server
but if the timeout is null (equal to 0), there will be no timeout on server and no automated unlocking, so do not schedule a sync every 5 seconds to check for it