Fix conflicting job states after restart #919
Merged
+5
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DosenSuppe
added
bug
1nf0rmagician
requested changes
Dec 11, 2025
1nf0rmagician
force-pushed
the
port/FixAwaitJobEventsOnShutdownToFuture
branch
from
fc74004 to
c6da7fb
Compare
1nf0rmagician
approved these changes
Jan 6, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem:
The JobManager detaches the JobChanged event. That causes that the Stop execution proceeds and the Stop of Joblist overcomes the changed events.
Solution:
Yield for every job to stop before continuing.
(cherry picked from commit 3e44339be332e5feb167e4d283dc283f695c9f9f)