Skip to content

chore: improve rust blocking behavior#824

Merged
ajewellamz merged 8 commits intomain-1.xfrom
ajewell/rust-blocking
Jan 23, 2026
Merged

chore: improve rust blocking behavior#824
ajewellamz merged 8 commits intomain-1.xfrom
ajewell/rust-blocking

Conversation

@ajewellamz
Copy link
Contributor

Issue #, if available:

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@ajewellamz ajewellamz requested a review from a team as a code owner January 22, 2026 21:32
seebees
seebees previously approved these changes Jan 22, 2026
Copy link
Contributor

@seebees seebees left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At a high level, this looks good to me.

robin-aws
robin-aws previously approved these changes Jan 23, 2026
Copy link
Contributor

@robin-aws robin-aws left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM assuming we fix the missing CI checks and they pass :)

robin-aws
robin-aws previously approved these changes Jan 23, 2026
@ajewellamz ajewellamz merged commit 351cff6 into main-1.x Jan 23, 2026
87 checks passed
@ajewellamz ajewellamz deleted the ajewell/rust-blocking branch January 23, 2026 20:08
@@ -0,0 +1,27 @@
async fn async_fn() {
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can these tests assert that ~100 milliseconds passed? Or some such assertion that the future was run to completion and not dropped

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.

4 participants