Skip to content
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

Use ropt events instead of querying server for optimization status #9957

Open
oyvindeide opened this issue Feb 4, 2025 · 0 comments · May be fixed by #10213
Open

Use ropt events instead of querying server for optimization status #9957

oyvindeide opened this issue Feb 4, 2025 · 0 comments · May be fixed by #10213
Assignees

Comments

@oyvindeide
Copy link
Collaborator

Currently we are querying the server for the optimization status, but we should instead use the events that are available from the WebSockets end-point. In the first iteration we can just duplicate the current output to the cli, and we can improve the visuals later.

Blocked by:
#9956 and #9001

@oyvindeide oyvindeide moved this to Todo in SCOUT Feb 4, 2025
@yngve-sk yngve-sk removed the blocked label Feb 25, 2025
@frode-aarstad frode-aarstad self-assigned this Mar 4, 2025
@frode-aarstad frode-aarstad moved this from Todo to In Progress in SCOUT Mar 4, 2025
@frode-aarstad frode-aarstad linked a pull request Mar 5, 2025 that will close this issue
9 tasks
@frode-aarstad frode-aarstad moved this from In Progress to Ready for Review in SCOUT Mar 5, 2025
@oyvindeide oyvindeide moved this from Ready for Review to Reviewed in SCOUT Mar 6, 2025
@frode-aarstad frode-aarstad moved this from Reviewed to Ready for Review in SCOUT Mar 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Ready for Review
Development

Successfully merging a pull request may close this issue.

3 participants