-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[CNVM] Unify error handling UX #155449
Comments
@opauloh verified to me it doesn't happen after fixing the mappings |
Tested with @nick-alayil this doesn't happen anymore on new instance |
Reopening the issue to improve our error handling |
Related to this issue, another tech debt from the past: #152944 (comment) |
could be related issue: #157954 |
Motivation
When handling unexpected errors the table disappears (examine screenshot)
The preferred way would be to show the table with its previous state and have a toaster notification about the error without affecting the current state when the server returns an error.
Origin issue (when mapping where missing)
Describe the bug
Not all of the fields in the findings table of vulnerability are mapped.
This PR should have solved this:
For some reason when I've had a system with pre-existing vulnerabilities, it wasn't handled (attempted to run a new transform).
This did not help and I would have expected my index to be updated.
I can also see the old mappings in the index.
Expected behavior
The table shouldn't crash when we sort any fields.
Screenshots
The text was updated successfully, but these errors were encountered: