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

Fix non existing report in the GUI #1641

Merged
merged 1 commit into from
Jul 10, 2018

Conversation

csordasmarton
Copy link
Contributor

Closes #1469

If no report can be found based on the given URL, remove the report hash and the report id from the URL.

Copy link
Contributor

@gyorb gyorb left a comment

Choose a reason for hiding this comment

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

I still can reproduce the problem described in the issue.

@csordasmarton csordasmarton requested a review from gyorb July 3, 2018 14:04
@Ericsson Ericsson deleted a comment Jul 3, 2018
@Ericsson Ericsson deleted a comment Jul 3, 2018
Copy link
Contributor

@gyorb gyorb left a comment

Choose a reason for hiding this comment

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

If I store the same reports again (same hash ...) after a browser refresh the report with the same hash is not found based on the URL even if the report hash did not change.
I get these messages:

Object { errorCode: 0, message: "Report 10 not found!", extraInfo: null, stack: "" }  ListOfBugs.js:474:26
No report can be found: 034c556d3450455111ca03504ba6f4ec

If no report can be found based on the given URL, remove
the report hash and the report id from the URL.
@csordasmarton csordasmarton requested a review from gyorb July 10, 2018 07:35
@Ericsson Ericsson deleted a comment Jul 10, 2018
@gyorb gyorb merged commit 49b5965 into Ericsson:master Jul 10, 2018
@csordasmarton csordasmarton deleted the fix-gui-no-report branch July 11, 2018 08:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants