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

chore: copy plan marks when applying merge group #443

Open
wants to merge 1 commit into
base: transition-to-runkit
Choose a base branch
from

Conversation

wvmcastro
Copy link

@wvmcastro wvmcastro commented Dec 5, 2024

Depends on:

This became a necessity as we pretend to do early deployments at network generation. In this scenario, when a "free" task context is merged into its deployed counter part its plan marks is not carried out to the deployment task instance. Then, this task instance would be garbage collected because it did not carried the permanent mark from the replace "free" task context

https://buildbot.tidewise.io/#/builders/1791/builds/7

@wvmcastro wvmcastro requested a review from doudou December 6, 2024 19:08
@wvmcastro wvmcastro force-pushed the copy-merged-task-plan-marks branch 2 times, most recently from 94b4661 to f78ca1d Compare December 10, 2024 13:07
This became a necessity as we pretend to do early deployments at network
generation. In this scenario, when a "free" task context is merged into its
deployed counter part its plan marks is not carried out to the deployment task
instance. Then, this task instance would be garbage collected because it did
not carried the permanent mark from the replace "free" task context
@wvmcastro wvmcastro force-pushed the copy-merged-task-plan-marks branch from f78ca1d to 4edb33a Compare December 18, 2024 20:53
@solver = Syskit::NetworkGeneration::MergeSolver.new(@local_plan)
end

# I don't like the "destination task" name but couldn't thought in a better one
Copy link
Member

Choose a reason for hiding this comment

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

Better make that a comment in the PR itself. ... now you have to remove it :P

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