brokkoli_ori has quit [Quit: bye people (Leaving)]
<oz>
ah, I'm sure we'll see more and more. Crystal is a joy to work with. :)
ur5us_ has quit [Ping timeout: 255 seconds]
onyx has joined #crystal-lang
_ht has joined #crystal-lang
jmdaemon has quit [Ping timeout: 246 seconds]
ur5us_ has joined #crystal-lang
ur5us_ has quit [Remote host closed the connection]
ur5us has joined #crystal-lang
<FromGitter>
<stellarpower> Should I open this as a bug?
<FromGitter>
<stellarpower> Re the specific error it comes back with
<FromGitter>
<Blacksmoke16> can you reproduce it without torify?
<FromGitter>
<Blacksmoke16> a minimal, reproducible example would be great to have
<FromGitter>
<stellarpower> I would, but without knowing what the conditions are that caused it, I assume it'd take thousands of requests before seeing the same thing crop up again
<FromGitter>
<Blacksmoke16> like manually grab the response string, save it to a heredoc const, new up an IO::Memory, and see if that also causes the error?
<FromGitter>
<Blacksmoke16> er the nilable version, `from_io?` as thats what the client is using
ur5us has quit [Ping timeout: 255 seconds]
<FromGitter>
<stellarpower> As in, get the encrypted data from the socket, then get HTTP::Response ot try and parse this fro mthe buffer directly.?
<FromGitter>
<Blacksmoke16> i was kinda assuming the response is simple, but if its large or something that might not work out too great