Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SBCL itself is already doing the exact same thing, see:
https://github.com/sbcl/sbcl/blob/master/contrib/sb-simple-streams/internal.lisp#L656
which calls: https://github.com/sbcl/sbcl/blob/master/src/code/fd-stream.lisp#L2285-L2292
In my case, I ended up going down that rabbit hole because the FD reported by
source
(i.e. the underlying fd-stream), aka(sb-sys:fd-stream-fd (slot-value ironclad:*prng* 'ironclad::source))
, had a different file descriptor in/proc/$pid/fd/
. The behavior I was observing was a stuck read -- most likely because the real file descriptor stored in fd-stream was a socket.I assume it is related to double-closing, one way or another.