Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't retain passive clocks at top-level #4198

Merged
merged 5 commits into from
Nov 1, 2024
Merged

Conversation

toots
Copy link
Member

@toots toots commented Oct 31, 2024

No description provided.

@toots toots force-pushed the weak-queue-passive-clocks branch from 89c48d4 to 575b26c Compare October 31, 2024 14:53
@toots toots force-pushed the weak-queue-passive-clocks branch from 575b26c to a69db6e Compare October 31, 2024 16:06
@toots toots changed the title Keep passive clocks in a weak queue. Don't retain passive clocks at top-level Nov 1, 2024
@toots toots enabled auto-merge November 1, 2024 21:57
@toots toots added this pull request to the merge queue Nov 1, 2024
Merged via the queue into main with commit 63abaa4 Nov 1, 2024
25 checks passed
@toots toots deleted the weak-queue-passive-clocks branch November 1, 2024 22:33
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.

1 participant