-
Notifications
You must be signed in to change notification settings - Fork 9
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
[general need] Mia loses the name of the brick in case of a calculation launch error (e.g. a pipeline without input parameters) #258
Comments
Other name issue has been noticed. See the ticket #263. |
The "main" name comes from the capsul.pipeline.pipeline_workflow.workflow_from_pipeline() method when the pipeline is in fact a single process. Maybe I'm missing something (maybe there's a reason for using 'main' as the name in all cases?) but as this is a pipeline with a single process, the node must take the name of the class + '_1'. So, I think this line should be: @denisri, what do you think? |
No problem, it's fine... it was just a bit of code done too quickly. |
Done. |
The minimum steps to reproduce :
=> Except for the problem of the name of the brick, the case is well managed now (following the previous opened ticket on this subject).
If we now want to get things right:
We see on the status bar: Pipeline "NoName" has been correctly run
![issue1](https://user-images.githubusercontent.com/37933899/157635884-d7287c5e-4995-4a78-baf7-f76064a770fa.png)
![issue2](https://user-images.githubusercontent.com/37933899/157636306-d06f8a60-82cf-443f-a703-f6066e28918e.png)
We see on the stdout:
And we see in DataBrowser for the Bricks tag (this is the most important problem, as we lose the data history in this case) :
EDIT: If we hit the
main
button, mia crashs with this exception:The text was updated successfully, but these errors were encountered: