wstransport.nim: avoid re-raising 'TransportOsError' to avoid stopping switch.accept
#929
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.
Description
We found that a 'TransportOsError' can be raised by the next:
https://github.com/status-im/nim-libp2p/blob/224f92e17251464984d6906316c54d2e1108ae43/libp2p/transports/wstransport.nim#L260
Then, that 'TransportOsError' exception was re-raised in
wstransport
and caught by theswitch.accept
proc, which made the main accept loop end accepting new upcoming connections because 'TransportOsError' is 'CatchableError'.https://github.com/status-im/nim-libp2p/blob/224f92e17251464984d6906316c54d2e1108ae43/libp2p/switch.nim#L277
Impacted component
We saw the next problem in
nwaku
: waku-org/nwaku#1831Future enhancements
#927