Rémi Cardona
Rémi Cardona
Is there any chance for part or all of the new type checker code to be reverted until the issue is fixed? Thanks
This will be dealt with as part of the API redesign of #118. This callback (like most/all others) is most likely going to be removed altogether.
Well, it's not so much called as it's already running as a Task when the handshake is done. Given the current "error handling" code, yes this behavior looks correct. TBH,...
There are no workaround for now, and this is very unfortunate. I've come up with this issue myself and I'll see if I can't improve things somewhat. I'll report back...
> After I'm done with encoding/decoding module it will be possible to memoize encoding and decoding of types and frames. Do you think this could be useful? I'm not against...
which version of python are you using? maybe there's been a change in the standard library
Haven't tested locally, but that sounds about right. And it sucks! Thanks for reporting! A PR would be much appreciated or we'll try to fix it as time allows. Cheers
Sorry, no news unfortunately. Been busy with other work. A PR would be most appreciated. Thanks
Just to be 100% sure, did you try this on 0.15.0b1? I don't remember merging anything related to acks but just in case…
I'm not familiar with that feature. Do you have any sample code/configuration that shows the bad behavior?