[Sbcl-help] Stop a thread with SBCL ?

[XavierQ <xav...@ya...>]

Not an issue, more a call for help :


I am running an app written in Common Lisp with SBCL (Rigetti Forest 
SDK), everything was working fine.

Then my computer shutdown abruptly - battery problem - while running the 
app (in tmux).

Since then unable to launch the app and having the following message:

[name@name ~]$ quilc
Unhandled USOCKET:NS-TRY-AGAIN-CONDITION in thread #<SB-THREAD:THREAD 
"Version Check" RUNNING
{1004DDC4E3}>:
   Condition USOCKET:NS-TRY-AGAIN-CONDITION was signalled.

Backtrace for: #<SB-THREAD:THREAD "Version Check" RUNNING {1004DDC4E3}>
0: (SB-DEBUG::DEBUGGER-DISABLED-HOOK #<USOCKET:NS-TRY-AGAIN-CONDITION 
{1004F0ADC3}> #<unused argument> :QUIT T)
1: (SB-DEBUG::RUN-HOOK *INVOKE-DEBUGGER-HOOK* 
#<USOCKET:NS-TRY-AGAIN-CONDITION {1004F0ADC3}>)
2: (INVOKE-DEBUGGER #<USOCKET:NS-TRY-AGAIN-CONDITION {1004F0ADC3}>)
3: (ERROR USOCKET:NS-TRY-AGAIN-CONDITION :SOCKET NIL)
4: (USOCKET::HANDLE-CONDITION #<SB-BSD-SOCKETS:TRY-AGAIN-ERROR 
{1004F0ACB3}> NIL "downloads.rigetti.com")
5: (SB-KERNEL::%SIGNAL #<SB-BSD-SOCKETS:TRY-AGAIN-ERROR {1004F0ACB3}>)
6: (ERROR SB-BSD-SOCKETS:TRY-AGAIN-ERROR :ERROR-CODE -3 :SYSCALL 
"getaddrinfo")
7: (SB-BSD-SOCKETS::ADDRINFO-ERROR "getaddrinfo" -3)
8: (SB-BSD-SOCKETS:GET-HOST-BY-NAME #<unavailable argument>)
9: (USOCKET:GET-HOSTS-BY-NAME "downloads.rigetti.com")
10: (USOCKET:SOCKET-CONNECT "downloads.rigetti.com" 80 :PROTOCOL :STREAM 
:ELEMENT-TYPE FLEXI-STREAMS:OCTET :TIMEOUT 20 :DEADLINE NIL :NODELAY 
:IF-SUPPORTED :LOCAL-HOST NIL :LOCAL-PORT NIL)
11: (DRAKMA:HTTP-REQUEST #<PURI:URI 
http://downloads.rigetti.com/qcs-sdk/versions?quilc=1.23.0> :WANT-STREAM 
T :PROXY NIL)
12: (QUILC::QUERY-LATEST-SDK-VERSION :PROXY NIL)
13: (QUILC::SDK-UPDATE-AVAILABLE-P "1.23.0" :PROXY NIL)
14: ((LAMBDA NIL :IN QUILC::ASYNCHRONOUSLY-INDICATE-UPDATE-AVAILABILITY))
15: ((LAMBDA NIL :IN BORDEAUX-THREADS::BINDING-DEFAULT-SPECIALS))
16: ((FLET SB-UNIX::BODY :IN SB-THREAD::INITIAL-THREAD-FUNCTION-TRAMPOLINE))
17: ((FLET "WITHOUT-INTERRUPTS-BODY-4" :IN 
SB-THREAD::INITIAL-THREAD-FUNCTION-TRAMPOLINE))
18: ((FLET SB-THREAD::WITH-MUTEX-THUNK :IN 
SB-THREAD::INITIAL-THREAD-FUNCTION-TRAMPOLINE))
19: ((FLET "WITHOUT-INTERRUPTS-BODY-1" :IN SB-THREAD::CALL-WITH-MUTEX))
20: (SB-THREAD::CALL-WITH-MUTEX #<CLOSURE (FLET 
SB-THREAD::WITH-MUTEX-THUNK :IN 
SB-THREAD::INITIAL-THREAD-FUNCTION-TRAMPOLINE) {7F16ACD36CDB}> 
#<SB-THREAD:MUTEX "thread result lock" owner: #<SB-THREAD:THREAD 
"Version Check" RUNNING {1004DDC4E3}>> NIL T NIL)
21: (SB-THREAD::INITIAL-THREAD-FUNCTION-TRAMPOLINE #<SB-THREAD:THREAD 
"Version Check" RUNNING {1004DDC4E3}> NIL #<CLOSURE (LAMBDA NIL :IN 
BORDEAUX-THREADS::BINDING-DEFAULT-SPECIALS) {1004DDC48B}> NIL)
22: ("foreign function: call_into_lisp")
23: ("foreign function: new_thread_trampoline")

unhandled condition in --disable-debugger mode, quitting


My best guess is that the used socket and/or the thread were left - when 
my computer shutdown abruptly -  in a state (as a lock and/or in sleep) 
that resulted in the app now being unable to access them (the socket 
and/or the thread)

If anyone more knowledgeable than me in everything Lisp could suggest a 
path towards a solution, it would be much appreciated.