-
Notifications
You must be signed in to change notification settings - Fork 369
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
Panel with recent log/notification messages #4304
Comments
The next logical step once we have a global notifications panel would be to support categorizing warnings/errors per space view, and then add a badge to each space view that only counts the warnings for that specific space view, and redirects to the global notifications panel with a filter preset on click. |
There is a very related problem to this: In many situations we directly send TextLog messages to the Unfortunately, since introducing blueprints, we are no longer guaranteed that the TextLog heuristics will cause a It would be nice if this notification mechanism also let you review messages logged to |
This would be a nice feature to have in the Gradio component where a job is running on a remote server and console out isn't immediately visible to the user that kicked off the job in the space. |
Something like this would be really helpful. I just tried the app for the first time by loading it in the browser and opening a random gltf file I had lying around. It showed me 2 dozen warnings on the right, and before I was able to read even one of them completely, they were all gone again. For context, it was 38 times this:
|
Design notes here: https://www.notion.so/rerunio/Error-notification-panel-142b24554b1980c49d9ffce6e8da39ea First step here is to store recent logs, and implement a popup that displays them, and can be opened by pressing an icon in the top panel: |
I really want to add the minimal version of this, because the lack of this keeps biting us in the ass. |
All rerun log messages at INFO, WARN and ERROR levels are shown as popup "toasts" to the user. They linger for a few seconds, and then they are gone. It can be pretty annoying if there any many messages in a row, or if a message is big.
We should have a panel where the user can find these messages instead. @martenbjork has a design where we show a little number with unread messages:
We should show a scrollback of recent messages, and a red dot next to unread ones.
If we have such a view, then we could change the toast to not show long messages, and never more than one at a time, reducing the amount of noise in the viewer.
Example
log::info!("File saved to {path:?}");
Results in a shortened toast showing:
File saved to C:/Docu…
, and then a white1
in the title bar, indicating there is one unread INFO-level notification.The text was updated successfully, but these errors were encountered: