Maximilian Hils

Thanks for the detailed write-up! I have trouble reproducing this. Could you share your output after sending SIGUSR1 to mitmdump after a few invocations of client.py? Does running that have...

> I'm happy to continue using my workaround script, but maybe it'd be nice if there was a cli option to not store websocket messages? I think that generally makes...

Connection migration is not yet supported. We found during development that it introduces a lot of complexity and I made a call to nail down the basics first.

Not really - maybe you can expand what your high-level use case is? So far the ROI seems relatively low for this (lots of annoying complexity unfortunately), but I'd be...

Please 1) do not post tracebacks as screenshots and 2) provide full system information as in the issue template.

I can reproduce this error when shutting down mitmproxy, but I cannot reproduce this during operation. Can you folks clarify when you are hitting this?

To clarify: Do you see this *only* during shutdown (still a valid bug report of course), or also while mitmproxy is still running?

After some digging: I think this can only be triggered during shutdown, and this will be fixed by https://github.com/python/cpython/pull/113690, which will be part of Python 3.12.2.

mitmproxy 10.2.3 is out, which should fix this.

@Apurv428: Those are the three main areas of mitmproxy with some ideas for each area. Each area can have 0-N accepted projects, and of course proposals can also overlap between...