Closed christiankakesa closed 4 years ago
Good to see someone else is seeing this happening too. Well not good, just good to know I'm not alone. As far as I can tell the bug has to be in Crystal itself, because there's nothing really fancy going on in the HTTP client, and even if there were this should not be happening.
I just need to figure out what the factors are that lead to this issue occurring so that I can duplicate it outside of Crystal. Any help in that area would be much appreciated.
@fenicks do you think you could post a minimal working (or in this case breaking) example of a bot that results in this error happening?
@fenicks do you think you could post a minimal working (or in this case breaking) example of a bot that results in this error happening?
Yes, I will prepare a minimal working program this evening (from Paris).
@fenicks Much appreciated :) it could help narrow down the issue so I can get an issue report filed in the crystal-lang repo.
@fenicks I think I figured out the issue. Were you, by chance, trying to make requests from within a fiber? Go ahead and try the latest master branch update and see if it fixes your problem.
@watzon I use parallel
I my code which uses spawn
(Fiber
).
I didn't reproduce the bug because in my code I was using parallel but a dedicated HTTP::Client.
By using a new HTTP::Client
or the ConnectionPool
in the last commit it works.
Thanks.
Hi, I'm receiving the error below when sending message with my bot. I'm not sure if it's based on tourmaline, tourmaline's shards, or Crystal OpenSSL binding.
Can you help me understanding this error. Thanks.