Heraldo

> No-one should care about "bugs" that involve the user deliberately breaking things - sorry. You are reading from the filesystem, the folder is accessible to all programs running under...

> I think you can also reproduce that by killing poetry itself after it start cloning the github repo Here follows a reproduction of the same bug by terminating Poetry...

> IMO, it's fair enough to suppose the git repo got broken somehow and if there is a good way to detect this state, I assume we will accept a...

It was never "self-sabotage", all the 3 reproductions I made makes Poetry break by leaving a broken git clone at `venv/src/requests`. In a next installation of `requests` from git it...

I did include the `client_max_window_bits` parameter because that's what the Chrome browser does. I fixed it in my fork.

related https://github.com/nhooyr/websocket/issues/351

In my case the server always reply with `client_max_window_bits=15`, I made websocket accept that ```golang switch p { case "client_no_context_takeover": copts.clientNoContextTakeover = true continue case "server_no_context_takeover": copts.serverNoContextTakeover = true continue...

I meant the server replies with `client_max_window_bits=15` when the client sends `client_max_window_bits`, so it won't break this library Probably most servers do that