Skip over CDP errors, but record to an error log

[tmeasday]

What Changed

It seems various client.send() calls fail in circumstances we don't fully understand (e.g https://github.com/chromaui/chromatic/actions/runs/5618208830/attempts/1, and various customer reported issues).

It may be OK to ignore these errors -- in this PR, we skip over but record them to an errors.log. If resources are missing that are needed, we can refer to this log to see at what point the resource archiving failed.

How to test

I'm not sure how to reproduce the problem, but running the canary against a real project to make sure it still works is a good idea.

Change Type

• maintenance
• documentation
• patch
• minor
• major

[linear]

AP-3454 Error: cdpSession.send: Target closed at m.requestPaused

How is the user affected? And what is the expected behavior?

<Use plain english, think about what the user is trying to but cannot do.>

User's (including our own Chromatic E2E project) playwright tests will sporadically fail due to an error in the

requestPaused function

The error often looks like

cdpSession.send: Protocol error (Fetch.continueRequest): Invalid InterceptionId.

How many and/or what class of users does this impact?

<Examples are: All Github users, An estimated 30 Bitbucket users with expired tokens, etc …>

3 E2E beta users

Is there a workaround?

<If so, describe it.>

No

What are the steps for reproducing the issue?

<First, try to reproduce the issue. Be as precise as you can with the steps to help the developer and QA person save time. If you can't reproduce it, describe what you tried and add the Needs Repro label.>

TBD

Other information

[tmeasday]

🚀 PR was released in v0.0.18 🚀