-
Notifications
You must be signed in to change notification settings - Fork 34
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
KeyError: 'webSocketDebuggerUrl' #5
Comments
Actually, i think you can reproduce it if you open chrome dev tools in the browser (ctrl+shift+j). |
I can reproduce this when multiple clients are attached (which isn't supported by the protocol). Are you using Chromote and the browser at the same time? |
The simplest way to reproduce the issue is this:
At this point the exception should appear
If you close the chrome dev tools and run again the snippet the exception won't be launched. Btw, cool project of yours! |
It's not real solution but locally I've patched _get_tabs:
So i can use chromote having multiple browsers where many tabs will be using the ChromeDevTools... I won't get them back of course but at least Chromote won't crash. |
Great, why not send a PR. My preference would be to drop the parens and explicate call to
|
Nah, your choice, it's your baby ;-) For my use-case i've tweaked my local copy like this:
and adding one method to check "valid" tabs:
That way i have all available tabs from my browsers, if i want to reload one tab i just check first if is valid or not, it works wonderfully... That way i can run my scripts while other tabs have opened the chrome-dev-tools, workflow is fast. |
Hi, sometimes this exception is yield:
And the code yielding that exception is very basic
As i said, it happens sometimes but i don't know, any clue why?
Regards
The text was updated successfully, but these errors were encountered: