You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This involves being able to know the status of a pipeline, which we don't have access to right now.
My first idea was to have a field for that in the document and set it to the right status when the pipeline finishes, but for this the backend would need to be able to change data in the frontend.
Any ideas?
The text was updated successfully, but these errors were encountered:
Maybe we can modify our store in backend to write meta-data information about what workers finished and the total of workers for that pipeline (as we have _properties we can have _workers, _finished_workers, _running_workers or something like this). With this feature we won't have notion of time, but we'll have more information about what is happening on the pipeline (but only if we really need this information).
Having this or not, I think the status of a document can be one of these:
This does sound like a good idea, and the StoreProxy (in the frontend) can look at this metadata and show it better to the user.
We already know when there was an error ("_error" and "_exception" are created in the mongodb document). We just need to show the user which analysis the error affects.
I think to start we could have only status and show the contents of _exception if there is an error. Then the ability to re-run the pipeline for that document.
This involves being able to know the status of a pipeline, which we don't have access to right now.
My first idea was to have a field for that in the document and set it to the right status when the pipeline finishes, but for this the backend would need to be able to change data in the frontend.
Any ideas?
The text was updated successfully, but these errors were encountered: