Pierce Freeman

This issue tipped me off to a possible fix: https://github.com/psf/requests-html/issues/326. The root of the error is that `pyppeteer` is trying to send an exit signal to flask's secondary thread, which...

@kgritesh Also looking for the same worker process concurrency. Did you get started on a fork with the changed logic?

Seeing this same issue - anyone have advice on a solution? EDIT: temporarily workaround is to lock matplotlib at 2.0.2 via ``` pip install matplotlib==2.0.2 ```

@andymccurdy Stumbled upon this thread when investigating my own bug with decoding responses with binary data. Is the addition of a `r.responses_as_bytes` context manager still on the roadmap or have...

@barjin @wireguard-dev It seems like the biggest issue here is the lack of `init script` support in service workers. [worker-evaluate](https://playwright.dev/docs/api/class-worker#worker-evaluate) isn't a good fit because it can only be called...

@barjin I wrote a MITM proxying library to work around chromium issues where it won't intercept some traffic. It should support that ServiceWorker/SharedWorker use case over both http and https....

@wireguard-dev Can you elaborate a bit on what service blobs you're referring to? The proxy server should capture all packets that are going out the network, though. Just like providing...

@wireguard-dev This case gets us a bit outside the scope of the original thread, which was doing request interception over the network from shared workers. For this particular case I...

Seeing the same issue with `ping` requests. My workaround was to rewrite my handlers to use a nodejs-based proxy. I'm using [http-mitm-proxy](https://www.npmjs.com/package/http-mitm-proxy) since it can coexist in a node.js codebase...

Seeing the same thing on my end @mhils. Haven't yet gotten a chance to dig into the root cause behind this - but guessing it's some premature runloop termination that's...