-
Notifications
You must be signed in to change notification settings - Fork 32
🐛 [Frontend] Fix: start dynamic services #8224
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR fixes an issue with starting dynamic services in the frontend where a race condition was preventing proper initialization. The fix ensures that the progress sequence is created only after the node metadata is available.
- Moved progress sequence initialization from constructor to a property apply method
- Added conditional logic to handle cases where metadata may not be immediately available
- Implemented a listener to defer initialization until metadata becomes available
services/static-webserver/client/source/class/osparc/data/model/NodeStatus.js
Show resolved
Hide resolved
|
@mergify queue |
🛑 Configuration not compatible with a branch protection settingThe branch protection setting |
sanderegg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks
|
🧪 CI InsightsHere's what we observed from your CI run for 089abbb. ✅ Passed Jobs With Interesting Signals
|



What do these changes do?
Spotted by @sanderegg

This PR fixes the starting of dynamic services.
Notice the correct positioning and no errors popping up:

Related issue/s
How to test
Dev-ops