Fix async controllers deactivation regime #2017
Open
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.
Right now, we have the
wait_for_trigger_update_to_finish
method that waits for the current cycle to finish, but the problem would be the case when it is finished and a new cycle is triggered that means, even the previous cycle is finished, a new cycle might be triggered and this might cause segmentation fault, as the release interfaces is already called by deactivation method. This PR ensure to fix the issue