Ensure instance logs refresh after unsuspending an instance #2085
+3
−3
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.
Fixes #2083
Description
The logs view was clearing the refresh interval when an instance was in suspended state. However if the instance came out of suspended state it wasn't restoring the refresh interval so the logs would never update.
This keeps the interval running all the time the view is mounted - but only polls for logs if the state is not suspended.
It also clears the log history when we detect the instance is suspended; with the existing behaviour, when you suspended then started an instance the previous logs would be shown for a couple of seconds whilst it retrieved the new logs.
Related Issue(s)
#2083
Checklist
flowforge.yml
?flowforge/helm
to update ConfigMap Templateflowforge/CloudProject
to update values for Staging/ProductionLabels
backport
labelarea:migration
label