🎨♻️ [Frontend (& API)] Retire history from list latest services
#7292
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
odeimaiz
added
t:enhancement
|
mrnicegyu11
pushed a commit
to mrnicegyu11/osparc-simcore
that referenced
this pull request
Mar 26, 2025
…TISFoundation#7292) Co-authored-by: Pedro Crespo-Valero <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What do these changes do?
In this PR, the
historywhen listing latest services gets actually retired. This was a very expensive information to compute server-side and should speed up the start up time of the frontend.Frontend wise, since after this change the frontend doesn't know about the services' versions
history:/v0/catalog/services/{service_key}/{service_version}/v0/projects/{project_id}/nodes/-/servicesendpoint to be able to render on the dashboard card the information that was extracted from thehistory.This required quite some refactoring which is also part of this PR.
Before:
After:
Related issue/s
How to test
Dev-ops checklist