-
Notifications
You must be signed in to change notification settings - Fork 10k
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 that failing to open the password dialog once won't permanently disable it (PR 15335 follow-up) #16768
Ensure that failing to open the password dialog once won't permanently disable it (PR 15335 follow-up) #16768
Conversation
…y disable it (PR 15335 follow-up) *Please note:* This situation should never happen in practice, but it nonetheless cannot hurt to fix this. If the `PasswordPrompt.open` method would ever be called synchronously back-to-back *and* if opening of the dialog fails the first time, then the second invocation would remain pending indefinitely since we just clear out the capability.
/botio-linux preview |
From: Bot.io (Linux m4)ReceivedCommand cmd_preview from @Snuffleupagus received. Current queue size: 0 Live output at: http://54.241.84.105:8877/5342612bc1e6be5/output.txt |
From: Bot.io (Linux m4)SuccessFull output at http://54.241.84.105:8877/5342612bc1e6be5/output.txt Total script time: 1.42 mins Published |
…rivate as intended
/botio unittest |
From: Bot.io (Linux m4)ReceivedCommand cmd_unittest from @Snuffleupagus received. Current queue size: 0 Live output at: http://54.241.84.105:8877/17d52efaad46704/output.txt |
From: Bot.io (Windows)ReceivedCommand cmd_unittest from @Snuffleupagus received. Current queue size: 0 Live output at: http://54.193.163.58:8877/56f97dfd5f843cc/output.txt |
From: Bot.io (Linux m4)SuccessFull output at http://54.241.84.105:8877/17d52efaad46704/output.txt Total script time: 2.55 mins
|
From: Bot.io (Windows)SuccessFull output at http://54.193.163.58:8877/56f97dfd5f843cc/output.txt Total script time: 11.93 mins
|
Thanks! |
Please note: This situation should never happen in practice, but it nonetheless cannot hurt to fix this.
If the
PasswordPrompt.open
method would ever be called synchronously back-to-back and if opening of the dialog fails the first time, then the second invocation would remain pending indefinitely since we just clear out the capability.