Daniel Hahler
Daniel Hahler
Wouldn't `g:qf_auto_open_quickfix` / `g:qf_auto_open_loclist` do this for you then? Have you changed those settings? (they are on by default IIRC)
Oh, I see. Found https://github.com/aio-libs/aiohttp/issues/320 and https://github.com/aio-libs/aiohttp/issues/863 now. Might be worth having a clearer error here - I assume it waits for "HTTP/1" or something similar, and could detect "HTTP/2"...
@bourdeau > It seems that when I overload the app with Locust, if I stop the Locust connections, the app raises this Exception. Looks like a different issue / cause....
Can you reproduce it with a smaller example? In general, `BdbQuit` is what is used to quit pdb/bdb, and it might be shown although it should not.
This works with pdb++ from the master branch, please test it there.
Installation via pip should work (via local checkout (`pip install …/pdpbb` or `pip install 'git+https://github.com/pdbpp/pdbpp@master'`).
Confirmed. This fixes it, but likely needs checks to handle / skip it with older Pythons, and I am not sure if classes should be used as-is really: ```diff src/pdbpp.py...
Let's keep the issue open until a fix is committed.
This works better with pdb++ from the master branch, please test it there.
I think it might make sense to have this as a default behavior even, i.e. only rules with `apply_on_restart=true` would be applied during restart. The handling of floating clients gets...