Skip to content

fix: correctly handle situation where a socket has been closed but the other side is still writing to it #40

fix: correctly handle situation where a socket has been closed but the other side is still writing to it

fix: correctly handle situation where a socket has been closed but the other side is still writing to it #40

Triggered via pull request November 12, 2024 15:01
Status Success
Total duration 34s
Artifacts

unit_tests.yaml

on: pull_request
unit_tests
23s
unit_tests
Fit to window
Zoom out
Zoom in