Skip to content

fix: resolve Await waiters individually instead of broadcasting - #1196

Open
roger2hk wants to merge 1 commit into
transparency-dev:mainfrom
roger2hk:fix-awaiter-block
Open

roger2hk wants to merge 1 commit into
transparency-dev:mainfrom
roger2hk:fix-awaiter-block

Conversation

@roger2hk

Copy link
Copy Markdown
Contributor

Fixes #1192.

@roger2hk
roger2hk requested a review from AlCutter September 24, 2026 13:56
@roger2hk
roger2hk marked this pull request as ready for review September 24, 2026 13:57
@roger2hk
roger2hk requested a review from a team as a code owner September 24, 2026 13:57
@AlCutter

Copy link
Copy Markdown
Collaborator

I'm not sure that #1192 is a valid bug.

Do you still want to continue with this PR for other reasons? At first glance it seems like a much heavier approach so it'd be worth understanding what this would buy us (a time & memory benchmark comparing before/after might be worthwhile, too).

This branch has not been deployed

No deployments
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.

PublicationAwaiter.Await never returns for log without a checkpoint, regardless of ctx cancellation/expiration

2 participants