QC-1105 Avoid "Unable to find object" at 2nd STOP in (Slice)TrendingTask #2157
Conversation
This file contains 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
Done so by proper cleanup before initializing objects in initialize(). Also, we reset the trend, so the 2nd run will start from an empty trend, just as the 1st would and should. Picking up an existing trend still is still a possibility of course.
Barthelemy
approved these changes
Feb 27, 2024
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.
Done so by proper cleanup before initializing objects in initialize(). Also, we reset the trend, so the 2nd run will start from an empty trend, just as the 1st would and should. Picking up an existing trend still is still a possibility of course.