Jan Rychter

FWIW, this `advice-add` fixed the breakage with consult for me nicely. It seems it wasn't pulled into the main hotfuzz codebase, though.

Just wanted to say thank you for writing hotfuzz. This is by far the best completion I've ever tested in Emacs (and I've tested quite a few). The C library...

That's the first thing I checked. Absolutely nothing changed server-side recently, and that includes not just the app and libraries, but also the entire server stack. I even rebooted the...

Thank you for offering to help! No, this is not a total showstopper, because it doesn't affect all connections, just a select few. I don't think changes in browser behavior...

Thanks to the kindness of my users, I now have traces of a normal page/app reload and a failed one, in Chrome. There are no console messages appearing in Chrome,...

After some more debugging, deploying versions with extended logging, and a number of tests: it appears that it is Sente that is killing the websocket connections, specifically because of a...

> * The most important problem is that some users could not log in, correct? Yes. Although I would not focus on the "log in" part too much — for...

I use http-kit 2.7.0, mostly with defaults. The only parameters to `http-kit/run-server` are increased `:max-body` and vastly increased `:max-ws` (I normally use 64MB, I increased this to 128MB for testing...

Well, now that I have the problem reproducible, testing this hypothesis is easy. I added `:thread 64` to `http-kit/run-server` option map. It did not change anything in the behavior. I...

To provide some context: I don't really have the option of sending data via different channels. The whole point of using Sente in my application is to tie the client...