Skip to content

Rescue error on disposeBrowserContext when context is missing#545

Closed
jvon1904 wants to merge 1 commit intorubycdp:mainfrom
jvon1904:missing-context-bugfix
Closed

Rescue error on disposeBrowserContext when context is missing#545
jvon1904 wants to merge 1 commit intorubycdp:mainfrom
jvon1904:missing-context-bugfix

Conversation

@jvon1904
Copy link
Copy Markdown

See my comments on Issue #540.

crahles added a commit to fuchs-eule/ferrum that referenced this pull request Sep 16, 2025
@route
Copy link
Copy Markdown
Member

route commented Feb 16, 2026

Proper fix should ignore default implicit context as in #566

@route route closed this Feb 16, 2026
crahles added a commit to fuchs-eule/ferrum that referenced this pull request Apr 20, 2026
…rror

Newer Chromium builds can report a "lost execution context" with the
phrase "Failed to find context with id <N>" instead of the historical
"Cannot find context with specified id". Match both so the error is
classified as a recoverable NoExecutionContextError (the client's retry
path) rather than bubbling up as a generic BrowserError.

This is the client.rb half of the previously ported rubycdp#545.
The contexts.rb half is dropped on rebase because upstream rubycdp#566
(56a46cd) addresses the underlying "dispose on missing context" issue
with a different, preferable approach (filter browser#reset against
Target.getBrowserContexts).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants