https://kotlinlang.org logo
#ktor
Title
# ktor
s

serebit

06/21/2019, 4:50 AM
The CIO client doesn't seem to respond to SIGINT now with 1.2.2... I assume I'm not the only one seeing this. Is there any way to restore the prior behavior, or a recommendation for how to compensate for it? My bad
👀 1
I see you @e5l... I believe this may be an issue with websockets specifically, if that helps
c

cy

06/21/2019, 9:41 AM
Shutdown hooks were added to server, not clients
I am not sure if it should be done in client at all
s

serebit

06/21/2019, 3:04 PM
I'm not talking about shutdown hooks here. I'm saying that when a Ktor application with an active websocket receives a signal to exit, it ignores it completely in 1.2.2, whereas in 1.2.1 it would honor the signal and the process would exit.
Actually... I'll need to take another look at my code. It seems like the semantics of websockets have changed pretty significantly
Yeah, it was the switch to daemon threads that significantly changed how my code behaved on exit. I fixed it, sorry for the confusion
12 Views