-
Notifications
You must be signed in to change notification settings - Fork 8
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
removes comm outages from signal monitor #418
Merged
chiaberry
merged 4 commits into
production
from
1585_remove_comm_outages_from_signal_monitor
Jun 21, 2024
Merged
Changes from 3 commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
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.
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 don't think this approach is going to work, because this component is used by other dashboards, e.g. the cameras dashboard:
![Screenshot 2024-05-29 at 10 59 37 AM](https://private-user-images.githubusercontent.com/14793120/334852049-6e682015-0705-4c6c-a4a9-4864e5c61b30.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk3NDgyNzQsIm5iZiI6MTcxOTc0Nzk3NCwicGF0aCI6Ii8xNDc5MzEyMC8zMzQ4NTIwNDktNmU2ODIwMTUtMDcwNS00YzZjLWE0YTktNDg2NGU1YzYxYjMwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MzAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjMwVDExNDYxNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTY1ZWUwMjZkM2VlNGMxYjgyN2M2ZmM3NDRjNWY4NTE5Y2RiNTM2Zjc3NTZkMzQzNjMxOGE5ZjhiOGIyZjI5YzAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.47aKOgpuaEZGFa98aTH0WnxKcDaK7F_EU6a2uT6s8Y8)
The other problem is that this message displays if you search the list when there is a signal outage:
![Screenshot 2024-05-29 at 11 00 26 AM](https://private-user-images.githubusercontent.com/14793120/334852312-886f12d6-a360-43dc-8c9e-59d5ad1dd04b.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk3NDgyNzQsIm5iZiI6MTcxOTc0Nzk3NCwicGF0aCI6Ii8xNDc5MzEyMC8zMzQ4NTIzMTItODg2ZjEyZDYtYTM2MC00M2RjLThjOWUtNTlkNWFkMWRkMDRiLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MzAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjMwVDExNDYxNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTBmZThhZjEzMWI2OWY2NjUwNDRiODBlMjZmODI3ZGU2YzM0Mjk4Y2Q1NjIzZmMzMTA1MjA4NjEyYTlhNDA5MzImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.tAKbzmWesK5k4vmNFMLBgImSsHgDyKR3XnIhsj4A0ws)
I guess one more problem is that i think this "everything is ok" message will display if there is an HTTP error returned from the Socrata query—e.g. if there is a socrata outage. just looking very quickly at the code, i'm not sure we currently display an error message under any circumstances.
From a styling perspective, it would be nice if the message rendered inside a list item with the same padding as other list items. Maybe using a green alert banner or something besides just plain text?
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 did not think to check if the component is used by other dashboards! thank you for pointing that out. and on your second and third point you're totally right i need to use a more robust way of checking why there might not be data returned from socrata. and i can definitely add styling to the message. @johnclary should we break these up into two issues (one to remove comm outages and one to display a message stating everything is working) or should i rework this?
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 know you asked John, but my opinion is to rework this
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 defer to Chia and Christina! 👍 🙏