Flow triggers wait #22
Merged
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
oliver-sanders
commented
Apr 12, 2022
| @@ -1403,7 +1403,7 @@ def spawn_task( | |||
| self.workflow_db_mgr.pri_dao.select_task_outputs( | |||
| itask.tdef.name, str(itask.point)) | |||
| ).items(): | |||
| if set(flow_nums).intersection(fnums): | |||
| if flow_nums.intersection(fnums): | |||
There was a problem hiding this comment.
flow_nums is already a set.
oliver-sanders
commented
Apr 12, 2022
| if flow[0] == FLOW_ALL: | ||
| flow_nums = self._get_active_flow_nums() | ||
| elif flow[0] == FLOW_NEW: | ||
| flow_nums = {self.flow_mgr.get_new_flow(flow_descr)} |
There was a problem hiding this comment.
Because this was within the for name, point in future_tasks loop this was creating a new flow for each triggered task rather than for each trigger event.
|
Brilliant, good spot. Thanks. |
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.
Addresses one issue where a single
--flow=newtrigger can result in multiple new flows, e.g. in the following example three new flows would be created:$ cylc trigger --flow=new <id>// //1/a //2/a //3/aAlso add a test to cover the behaviour of
--flow=allwhen multiple flows are present.