Skip to content
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

Merged
merged 1 commit into from
Jan 7, 2021

Conversation

csordasmarton
Copy link
Contributor

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:
image

@csordasmarton csordasmarton added GUI 🎨 usability 👍 Usability-related features labels Dec 15, 2020
@csordasmarton csordasmarton added this to the release 6.16.0 milestone Dec 15, 2020
dkrupp
dkrupp previously requested changes Jan 7, 2021
Copy link
Member

@dkrupp dkrupp left a 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
Copy link
Member

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.
@csordasmarton csordasmarton force-pushed the handle_missing_report branch from 6734664 to bb507d3 Compare January 7, 2021 13:41
@csordasmarton csordasmarton requested a review from dkrupp January 7, 2021 13:42
@bruntib bruntib dismissed dkrupp’s stale review January 7, 2021 16:08

The patch has been fixed.

@bruntib bruntib merged commit 1149cbe into Ericsson:master Jan 7, 2021
Copy link
Member

@dkrupp dkrupp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
GUI 🎨 usability 👍 Usability-related features
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants