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
If the inputs of a computational node that has been executed change, the state of the node would change from "Success" to "modified".
At some point (I guess with PATCH node), we lost this feature and therefore the frontend can't paint the nodes and edges that are out of date orange. We need to bring back a mechanism to let the backend notify the frontend about changes in the states.
I believe the reason is that when the backend is running a pipeline, it keeps the frontend updated with websocket messages (nodeUpdated). Since we introduced the PATCH, the frontend patches, but it doesn't get an updated state in the response, hence the status of the outputs get outdated.
If the inputs of a computational node that has been executed change, the state of the node would change from "Success" to "modified".
At some point (I guess with PATCH node), we lost this feature and therefore the frontend can't paint the nodes and edges that are out of date orange. We need to bring back a mechanism to let the backend notify the frontend about changes in the states.
PR when this was implemented:
ITISFoundation/osparc-simcore#2153
Currently:
After reloading, the status is fetched:
Event Horizon
The text was updated successfully, but these errors were encountered: