-
Notifications
You must be signed in to change notification settings - Fork 77
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
feat: hint banners in /status page #307 #418
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.
One small nitpick (the one about warning showing when refreshing the page is mostly what I'm asking about)
${duplicateURLS.join( | ||
", " | ||
)}. Something might be wrong with backend configuration.`; |
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.
another nitpick, but maybe extract duplicateURLS.join
to a separate variable (to avoid long expression inside)
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.
I guess i'm merging it like it is.
${duplicateURLS.join( | ||
", " | ||
)}. Something might be wrong with backend configuration.`; |
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.
I guess i'm merging it like it is.
Your checklist for this pull request
What is the current behaviour?
Currently user might not be aware of possible unwanted backend settings.
What is the new behaviour?
Now user receives warnings on
/status
page which warn them about missing agents, multiple agents connected with the same ursa_url or if it is advised to compact their datasets.Test plan
Either backend setup should be messed up with or stub data filled into backend responses. Unfortunately I'm not currently aware of better methods without further messing with frontend code.
Closing issues
fixes #307