Skip to content

Conversation

@younata
Copy link
Member

@younata younata commented Nov 28, 2025

This one is wild, because apparently, RunLoop.run(mode:before:) wasn't actually blocking for the amount of time specified. It was basically spinning the runloop once, then returning. This change now continuously spins the runloop until either the timeout passes, or a result is set.

The PR should summarize what was changed and why. Here are some questions to
help you if you're not sure:

  • What behavior was changed?
  • What code was refactored / updated to support this change?
  • What issues are related to this PR? Or why was this change introduced?

Checklist - While not every PR needs it, new features should consider this list:

  • Does this have tests?
  • Does this have documentation?
  • Does this break the public API (Requires major version bump)?
  • Is this a new feature (Requires minor version bump)?

…expectations

This one is wild, because apparently, RunLoop.run(mode:before:) wasn't actually blocking for the amount of time specified. It was basically spinning the runloop once, then returning.
This change now continuously spins the runloop until either the timeout passes, or a result is set.
@younata younata merged commit 96ac61f into main Nov 28, 2025
12 of 13 checks passed
@younata younata deleted the fix-broken-pollawait branch November 28, 2025 18:04
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