Skip to content

Conversation

@tesonep
Copy link
Collaborator

@tesonep tesonep commented Aug 25, 2025

  • Adding a flag to handle if the socket is blocked in a send.
  • Handling the async event for this case.

Fix #939

- Handling the async event for this case.
@tesonep
Copy link
Collaborator Author

tesonep commented Oct 17, 2025

I have tried, and it looks like it fixes also #1018

@mumez
Copy link

mumez commented Oct 17, 2025

Just to clarify: The issue on #1018 is only reproduced on the latest Linux VM, but this PR fixes the common part, not the platform-specific part. So, I am unsure how this code resolved the Linux-specific issue.

Could you attach some test code? I'll also test by myself.

@tesonep tesonep merged commit 423b506 into pharo-project:pharo-10 Nov 17, 2025
1 check failed
@mumez
Copy link

mumez commented Nov 17, 2025

I hope that the issue at #1018 has been resolved. I'll reopen the issue if the error still occurs on the latest pharo10 branch VM.

@mumez
Copy link

mumez commented Nov 17, 2025

I think it would be nicer if we have a unit test that shows what has been resolved.

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.

Socket>>sendData: hot-spins if the other side is unresponsive

2 participants