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

fix: dont remove task count listener until it reaches 0 #5650

Merged
merged 1 commit into from
Jun 25, 2024

Conversation

TarikBR
Copy link
Contributor

@TarikBR TarikBR commented Jun 22, 2024

If waitUltilDone() is called when you have 2 or more other tasks, the first one that is changed will still have tasks to wait for, but when it finishes it won't run because it was removed early.
(translated)

If waitUltilDone() is called when you have 2 or more other tasks, the first one that is changed will still have tasks to wait for, but when it finishes it won't run because it was removed early.
(translated)
Copy link
Contributor

@Mathias-Boulay Mathias-Boulay left a comment

Choose a reason for hiding this comment

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

Good catch, it seems good to me

@Mathias-Boulay Mathias-Boulay merged commit df0b762 into PojavLauncherTeam:v3_openjdk Jun 25, 2024
1 check passed
artdeell pushed a commit that referenced this pull request Jul 3, 2024
… 0 (#5650)

If waitUltilDone() is called when you have 2 or more other tasks, the first one that is changed will still have tasks to wait for, but when it finishes it won't run because it was removed early.
(translated)
artdeell added a commit that referenced this pull request Jul 3, 2024
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