You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
output operation on closed SSL stream
[Condition of type SIMPLE-ERROR]
Restarts:
0: [RETRY] Retry SLIME REPL evaluation request.
1: [*ABORT] Return to SLIME's top level.
2: [ABORT] abort thread (#<THREAD "repl-thread" RUNNING {1002EB7FA3}>)
Backtrace:
0: ((:METHOD SB-GRAY:STREAM-FORCE-OUTPUT (CL+SSL::SSL-STREAM)) #<unavailable argument>) [fast-method]
1: (FORCE-OUTPUT #<CL+SSL::SSL-STREAM for #<FD-STREAM for "socket xxx.xxx.xxx.xxx:35752, peer: xxx.xxx.xxx.xxx:443" {10082339E3}>>)
2: (DEXADOR.BACKEND.USOCKET:REQUEST #<unavailable argument> :METHOD :POST :CONTENT "{\"bucketId\": \"b78178f0df3db6975dd20513\"}" :HEADERS (("Authorization" . "Password")))
3: ((LAMBDA ()))
It looks like in usocket.lisp an assumption is made that the stream is still open when force-output is called on it. A quick look at cl-plus-ssl would seem to indicate that using ssl-stream-handle can be used to see if a stream is still open. If the stream is not open then maybe the retry code in usocket.lisp should start a new connection?
The text was updated successfully, but these errors were encountered:
returns
It looks like in
usocket.lisp
an assumption is made that the stream is still open when force-output is called on it. A quick look at cl-plus-ssl would seem to indicate that usingssl-stream-handle
can be used to see if a stream is still open. If the stream is not open then maybe the retry code inusocket.lisp
should start a new connection?The text was updated successfully, but these errors were encountered: