fix: increase websocket timeout for background throttling #8005
Conversation
Signed-off-by: Benjamin Frueh <benjamin.frueh@gmail.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
max-nextcloud
left a comment
max-nextcloud
left a comment
There was a problem hiding this comment.
Makes sense to me.
|
/backport to stable32 |
|
/backport to stable31 |
|
Hello there, We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process. Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6 Thank you for contributing to Nextcloud and we hope to hear from you soon! (If you believe you should not receive this message, you can add yourself to the blocklist.) |
📝 Summary
Increase the messageReconnectTimeout to 70 seconds to account for the 60 second background JS timer throttle in Chromium.
This prevents false connection lost notifications when the editor tab is in the background.
Local tests showed throttled intervals of: 59892ms, 59929ms, 59867ms, 59929ms, 59864ms, 59880ms - consistently under 60 seconds. A 70 second timeout should provide enough buffer.