Will Keeling

The option isn't documented, but Selenium Wire allows mitmproxy options to be passed using the `mitm_` prefix to the option name (mitmproxy is the engine that Selenium Wire uses behind...

Thanks for this. I'll see if I can quieten these messages.

This seems to be a bug introduced in version 4.3.3. A short term fix is to downgrade to 4.3.2: ``` pip install selenium-wire==4.3.2 ``` Related to #389

Are you able to share the code you're using that generates the error?

Thanks. I've tried reproducing but I don't see the error. The versions I'm running: ``` selenium-wire==4.5.6 undetected_chromedriver==3.0.6 chromedriver==96.0.4664.45 ``` Can you confirm your versions of `undetected_chromedriver` and `chromedriver` are the...

Yes that's odd. I notice that the error is coming from the `driver.quit()` call but I don't see that call in your example code above. Can you share the code...

Just noticed that `quit()` is actually being invoked by `__del__` on the `v2.Chrome` instance, presumably when it's cleaned up. I notice you're using Windows so I'll try and reproduce on...

Sorry for the delay in coming back @taytanqbpass I've tried reproducing on Windows, using the same code as above but with my own local proxy (I used an instance of...

Thanks for raising this and sorry for the delay in replying. It looks as though you've hit the maximum open file descriptor limit on your machine. When you start each...

Selenium Wire still uses the old mitmproxy core, so this will likely continue to affect Selenium Wire (there's no plans to upgrade the proxy core at the present time). I'll...