Strange behaviour with multiple `upstream tasks` on a ShellT

Question

Strange behaviour with multiple `upstream tasks` on a ShellTask This works ``` brt commands = create brt command map adoc fp=updated adocs brt commands logged = log item=brt commands desc= BRT commands brts = shell task map command=brt commands upstream tasks= tomogram fps ``` This fails ``` brt commands = create brt command map adoc fp=updated adocs brt commands logged = log item=brt commands desc= BRT commands brts = shell task map command=brt commands upstream tasks= tomogram fps brt commands logged ```

Kyle McChesney · Answer

Not 100 sure what the issue is but the top example likely works if you add `unmapped tomogram fps ` to the upstream task Its kind of an interesting edge case between ` map` and `upstream tasks`

Nate · Answer

can you describe the failure or share logs

Philip MacMenamin · Answer

Just to be clear the top example appears to work already

Philip MacMenamin · Answer

``` 2022 04 19 12 56 09 0600 INFO prefect TaskRunner | Task create brt command 0 Starting task run 2022 04 19 12 56 09 0600 INFO prefect TaskRunner | Task create brt command 0 Finished task run for task with final state Success 2022 04 19 12 56 10 0600 INFO prefect TaskRunner | Task log Starting task run 2022 04 19 12 56 10 0600 INFO prefect log | BRT commands opt rml imod bin batchruntomo di gs1 home macmenaminpe tmp tmpovrvi7nb dirTemplate adoc cp 8 gpu 1 2022 04 19 12 56 10 0600 INFO prefect TaskRunner | Task log Finished task run for task with final state Success 2022 04 19 12 56 10 0600 INFO prefect TaskRunner | Task ShellTask Starting task run 2022 04 19 12 56 10 0600 INFO prefect TaskRunner | Task ShellTask Finished task run for task with final state Failed 2022 04 19 12 56 10 0600 INFO prefect TaskRunner | Task log Starting task run 2022 04 19 12 56 10 0600 INFO prefect log | updated Adoc files PosixPath gs1 home macmenaminpe tmp tmpovrvi7nb dirTemplate adoc 2022 04 19 12 56 10 0600 INFO prefect TaskRunner | Task log Finished task run for task with final state Success 2022 04 19 12 56 10 0600 INFO prefect FlowRunner | Flow run FAILED some reference tasks failed ```

Philip MacMenamin · Answer

< Kyle McChesney> this idea of doing `unmapped ` stuff in the upstream tasks is interesting I think I have to get my head around that for a second

Kyle McChesney · Answer

< Kevin Kho> we discussed this at somepoint do you happen to have the link around

Philip MacMenamin · Answer

ahh ok so the upstream tasks should not be included within the map

Nate · Answer

hold on because if your first example works then I m wrong one sec

Kyle McChesney · Answer

`upstream tasks= unmnapped tomogram fps unmapped brt commands logged `

Kyle McChesney · Answer

does that work If I recall the issue was that an upstream task parameter needed to get passed to each mapped instance By specifying unmapped you ensure that the same one is used

Philip MacMenamin · Answer

right within the map OK hold on I have to get into an annoying VPN and it kills Slack BRB

Kevin Kho · Answer

Kyle is right ```mapped task = task one map upstream tasks= unmnapped tomogram fps unmapped brt commands logged ``` should work if `tomogram fps` and `brt commands logged` are not mapped tasks

Kevin Kho · Answer

Making them mapped will map element 1 of the upstream list to element 1 of the downstream list as a dependency so you get weirdness is the lists are not the same length

Philip MacMenamin · Answer

can confirm < Kyle McChesney> is correct Nice

Dan Morris · Answer

Needed this for my own project so thank you