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

Add endpoint error page #3991

Merged
merged 13 commits into from
Nov 11, 2019
Merged

Add endpoint error page #3991

merged 13 commits into from
Nov 11, 2019

Conversation

KlapTrap
Copy link
Contributor

Add a view to see the recent errors for a given endpoint.
Add a link to the "red bar" that sends the user recent error page for a single endpoint.
Improved the look of the red bar (more inline with material design).
Add a link to the error page to download the error information as a json file.

@KlapTrap KlapTrap self-assigned this Oct 17, 2019
* master:
  Master test fixes (#3992)
  Fix npm audit error in dev dependency - handlebars used by istanbul & karma-coverage-istanbul-reporter - weird goings on in stratos (npm audit shows handlebars errors), vanilla   angular 7 app (shows no handlebars errors) and vanilla angular 8 app (no   handlabrs errors). Same istanbul and coverage dependencies in all   node_modules directories and same coverage dependency in all apps - In the end fixed via audit's recommendation to `npm update handlebars --depth 4`
  Update versions links in readme
  Fix v2-master references and goreportcard link
Copy link
Contributor

@richard-cox richard-cox left a comment

Choose a reason for hiding this comment

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

  • It would be really useful for the user to remove the red bar. Either hide it until another error comes in or clear all previous errors. If there are errors that haven't been cleared the bell icon could show a notification that would take user to errors page
  • Mentioned in comments, but it would be good to have the errors list as a list with all the sorting and filtering goodness and avoids sizeable white space areas. This could also show all errors and filter by endpoint
  • Endpoint errors should be cleared on disconnect, particularly for the case where the next user to connect is different from previous one
  • Warning bar shows on stepper components where we already have a notification on error. As its more noticeable now not sure if we should hide it?

@richard-cox richard-cox added needs attention This PR needs attention and removed in review labels Oct 31, 2019
@KlapTrap
Copy link
Contributor Author

It would be really useful for the user to remove the red bar. Either hide it until another error comes in or clear all previous errors. If there are errors that haven't been cleared the bell icon could show a notification that would take user to errors page

That's the plan but out of scope for this ticket.
See #3871.

Mentioned in comments, but it would be good to have the errors list as a list with all the sorting and filtering goodness and avoids sizeable white space areas. This could also show all errors and filter by endpoint

I intentionally didn't use the list to keep it simple. As is a time sorted list, I prefer the one item per row, it makes it easier to understand and makes it less cluttered.

Endpoint errors should be cleared on disconnect, particularly for the case where the next user to connect is different from previous one

Out of scope #2974.

Warning bar shows on stepper components where we already have a notification on error. As its more noticeable now not sure if we should hide it?

Maybe. If it was there before I'd err on the side of keeping it as it is for now.

Copy link
Contributor

@richard-cox richard-cox left a comment

Choose a reason for hiding this comment

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

Happy to merge once passed gates. I'll start looking at the out of scope github issues

@KlapTrap
Copy link
Contributor Author

KlapTrap commented Nov 1, 2019

@richard-cox I had an overnight epiphany and decided to fix the "Out of scope" issues. It was just a PITA without them. I'm almost done with them.

@KlapTrap KlapTrap removed the needs attention This PR needs attention label Nov 5, 2019
* master:
  Add clean routes to e2e-clean-remnants (#4007)
  Auth jetstream refactor (#3882)
  Remove page nav not needed
  Local user account docs (#3952)
  Fix go mod files (#3986)
  Update references following graduation
  Ensure build cache upload fail does not fail job (#3994)
  Fixes issue properly
  Preparation for 2.6.0 Release
  Fix alignment of user button on newer Firefox
  Fix cert gen on Mac OSX 10.15
@codecov-io
Copy link

Codecov Report

Merging #3991 into master will decrease coverage by 0.02%.
The diff coverage is 46.66%.

@@            Coverage Diff            @@
##           master   #3991      +/-   ##
=========================================
- Coverage   61.12%   61.1%   -0.03%     
=========================================
  Files         860     861       +1     
  Lines       29359   29422      +63     
  Branches     4294    4307      +13     
=========================================
+ Hits        17945   17977      +32     
- Misses      11414   11445      +31

@KlapTrap KlapTrap merged commit 31fba37 into master Nov 11, 2019
@KlapTrap KlapTrap deleted the endpoint-error-page branch November 11, 2019 13:14
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.

3 participants