-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
ignore protocol error from closing tab after Chrome has been killed #1592
Conversation
This seems to just ignore logging is there not an underlying issue to resolve? |
Eric's error is actually " The problem comes from the exception bubbling up and doing So, the error is right, the logging is just confusing things in this case. |
Ah, so the only issue was logging it! |
yeah, it's a little weird because We could get trickier and not exit until we've disconnected or not disconnect if we're going to exit, but if we've already exited Chrome I personally think we just don't care if the close tab command was issued before Chrome closed but too late to do anything. |
Hilarious. So this does actually does fix the error? It does appear it's just not logging a message. Maybe you can add comment? Can a test check this? |
I did add a comment :) More of a comment? I'm not sure we need a test. It's just suppressing the log when closing the tab in a browser that's already been closed. In a sense, it was already successful :) |
Maybe just link to #1583? It has all the details. |
582636f
to
574f864
Compare
done |
fixes #1583