<FromGitter>
<naqvis> for sure this is just a hack and it won't work properly in MT mode. Intention here is to show there are whole lot possibilities via which you can design your own solution
taupiqueur has joined #crystal-lang
ur5us has quit [Ping timeout: 250 seconds]
taupiqueur_ has joined #crystal-lang
taupiqueur has quit [Read error: Connection reset by peer]
taupiqueur_ has quit [Ping timeout: 268 seconds]
taupiqueur has joined #crystal-lang
szutt has joined #crystal-lang
taupiqueur has quit [Ping timeout: 250 seconds]
taupiqueur has joined #crystal-lang
taupiqueur has quit [Ping timeout: 252 seconds]
taupiqueur has joined #crystal-lang
taupiqueur has quit [Ping timeout: 256 seconds]
taupiqueur has joined #crystal-lang
taupiqueur has quit [Ping timeout: 260 seconds]
taupiqueur has joined #crystal-lang
<Elouin>
Hi, i wrote a small irc bot and it works over unencrypted connections, but with tls its not really connecting.
<FromGitter>
<naqvis> i believe if you do `socket.puts message + "\n\r\n"` should work
<FromGitter>
<naqvis> reason is `puts` appends new line `\n` if string passed doesn't end with that, and IRC requires the `\r\n` as the marker to mark the end of message
postmodern has joined #crystal-lang
<Elouin>
Doesn't seem to work with "\n\r\n". Also it works without ssl, so i dont think its an IRC specific problem.
taupiqueur has joined #crystal-lang
<Elouin>
socket.flush is what makes the difference.
<Elouin>
(had that in the `<<` version of my code but not the `puts` version.)
<Elouin>
but now the question is, why do i have to flush with openssl but not without.
taupiqueur has quit [Ping timeout: 256 seconds]
notzmv has quit [Ping timeout: 240 seconds]
taupiqueur has joined #crystal-lang
postmodern has quit [Quit: Leaving]
notzmv has joined #crystal-lang
hightower2 has quit [Remote host closed the connection]
hightower2 has joined #crystal-lang
hightower3 has joined #crystal-lang
hightower3 has quit [Remote host closed the connection]
szutt has quit [Quit: Ping timeout (120 seconds)]
szutt has joined #crystal-lang
<raz>
may be related to buffer sizes
<raz>
or buffering in general (i'm no familiar with ossl, but perhaps it generally only sends on flush or close?)
hightower2 has quit [Ping timeout: 252 seconds]
taupiqueur has quit [Ping timeout: 252 seconds]
hightower2 has joined #crystal-lang
hightower2 has quit [Ping timeout: 240 seconds]
notzmv has quit [Remote host closed the connection]
notzmv has joined #crystal-lang
szutt has quit [Quit: Client closed]
taupiqueur has joined #crystal-lang
taupiqueur has quit [Ping timeout: 268 seconds]
hightower2 has joined #crystal-lang
hightower2 has quit [Ping timeout: 252 seconds]
taupiqueur has joined #crystal-lang
taupiqueur has quit [Ping timeout: 252 seconds]
hightower2 has joined #crystal-lang
hightower2 has quit [Ping timeout: 256 seconds]
ur5us has joined #crystal-lang
taupiqueur has joined #crystal-lang
taupiqueur has quit [Ping timeout: 250 seconds]
ur5us has quit [Ping timeout: 252 seconds]
taupiqueur has joined #crystal-lang
ur5us has joined #crystal-lang
<SamantazFox>
How is the stack trace generated in cas of an exception?
<SamantazFox>
There seem to be some inconsistencies
<SamantazFox>
For instance, the stack trace provided in this issue: https://github.com/iv-org/invidious/issues/2713 looks weird starting from the line `from src/invidious/trending.cr:19:14 in 'trending' (and upwards)`
<SamantazFox>
I don't see where the `in 'trending'` comes from (it's not the function's name, like on other lines)
<FromGitter>
<oprypin:matrix.org> SamantazFox, that is quite weird indeed
<SamantazFox>
oprypin And the weirdest past comes later on in the trace (almost at the top) where you can clearly see one of our function (`decode_length_seconds`) being mapped to the stdlib `pointer.cr`