-
Notifications
You must be signed in to change notification settings - Fork 383
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
[gui] Handle missing report #3102
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.
please add the filename too to the link.
Resolution order should be
report id
bug hash and the report should be shown with the matching file name (if possible).
@@ -111,7 +111,7 @@ | |||
:to="{ name: 'report-detail', query: { | |||
...$router.currentRoute.query, | |||
'report-id': item.reportId ? item.reportId : undefined, | |||
'report-hash': item.reportId ? undefined : item.bugHash | |||
'report-hash': item.bugHash |
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.
Please also add the file name in the url of the reques to show the bug in the correct file in case the report id is missing.
The server will remove reports from the database which have the same report hash on run update. This can cause problem, when the user saves the URL which contains a report id which is actually removed from the database. For this reason we will save the report hash and the file path in the URL and if no report is found with the report id in the database we will falback and search the report by report hash and file path. If the report hash is not in the url or the report can not be found by the report id or report hash we will display this information to the user.
6734664
to
bb507d3
Compare
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.
LGTM
The server will remove reports from the database which have the same
report hash on run update. This can cause problem, when the user saves
the URL which contains a report id which is actually removed from
the database.
For this reason we will save the report hash in the URL and if
no report is found with the report id in the database we will falback
and search the report by report hash.
If the report hash is not in the url or the report can not be found
by the report id or report hash we will display this information to
the user.
Screenshot: