Skip to content

Conversation

@catamorphism
Copy link
Collaborator

The new tests are based on the previous simple test where the server accepts one connection and echoes back a message received from the client.

Scenarios tested:

  • Client hangs up after connecting
  • Client hangs up while sending
  • Client hangs up after sending
  • Client hangs up while receiving
  • Server hangs up after connecting but before receiving data from client
  • Server hangs up while receiving data
  • Server hangs up after receiving all data but before sending data back to client
  • Server hangs up while sending data back to client

As part of this testing, I implemented timeouts for TCP sockets. There are no tests for UDP sockets yet, so timeouts are not implemented yet for them.

@catamorphism catamorphism requested a review from pchickey October 14, 2025 23:29
…or TCP sockets

The new tests are based on the previous simple test where the server
accepts one connection and echoes back a message received from the client.

Scenarios tested:

* Client hangs up after connecting
* Client hangs up while sending
* Client hangs up after sending
* Client hangs up while receiving
* Server hangs up after connecting but before receiving data from client
* Server hangs up while receiving data
* Server hangs up after receiving all data but before sending data back to client
* Server hangs up while sending data back to client

As part of this testing, I implemented timeouts for TCP sockets.
There are no tests for UDP sockets yet, so timeouts are not implemented
yet for them.
@catamorphism catamorphism force-pushed the sockets-testing-hangups branch from 8ec291a to b7540c5 Compare October 18, 2025 21:21
@catamorphism catamorphism merged commit 1590774 into WebAssembly:main Oct 18, 2025
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants