fix: remove asynchronous code in network adaptation#549
Open
jhonasiv wants to merge 1 commit intotransition-to-runkitfrom
Open
fix: remove asynchronous code in network adaptation#549jhonasiv wants to merge 1 commit intotransition-to-runkitfrom
jhonasiv wants to merge 1 commit intotransition-to-runkitfrom
Conversation
This allowed that the adaptation plan would take conflicting updates from the network generation transaction, potentially breaking tasks with conflicting information (e.g. a task that was running conflicting with a plan update that should drop it, so executable was being unset)
doudou
approved these changes
Mar 15, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This allowed that the adaptation plan would take conflicting updates from the network generation transaction, potentially breaking tasks with conflicting information (e.g. a task that was running conflicting with a plan update that should drop it, so executable was being unset)