-
Notifications
You must be signed in to change notification settings - Fork 88
Description
Environment
7.2.1 something
Description
A forum came with a fragment of the viewer's log and showed that the viewer is walking away from the login service after 40 seconds and declaring a timeout.
The enhancement is to extend this out for the modern era and have more successful logins and fewer support calls. I don't have the login service's timeout in hand but something just beyond that.
A nice-to-have would be the viewer recognizing that login times have been approaching the local timeout value and to warn to take cleanup action (e.g. inventory). That with the usual 'dismiss/don't warn again/don't warn again today' sort of option.
Reproduction steps
You need a very big inventory or a slow network. Since this is likely a large payload, viewer will be creating backpressure and extending the response time on slow/lossy networks.
Test plan
Confirm debug setting LoginSRVTimeout defaults to 90.
This repo is using Opire - what does it mean? 👇
💵 Everyone can add rewards for this issue commenting
/reward 100 (replace 100 with the amount).🕵️♂️ If someone starts working on this issue to earn the rewards, they can comment
/try to let everyone know!🙌 And when they open the PR, they can comment
/claim #4730 either in the PR description or in a PR's comment.🪙 Also, everyone can tip any user commenting
/tip 20 @monty-linden (replace 20 with the amount, and @monty-linden with the user to tip).📖 If you want to learn more, check out our documentation.