You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we get a big ugly scary error page whenever the server crashes.
It seems like crashing will be a fairly normal thing for Pullup, so we should make this error page prettier. Here's the Heroku docs regarding the subject: https://devcenter.heroku.com/articles/error-pages
I also think we should have the log list on the error page, so that we can see clearer what caused the server to crash. That code is in a PR, waiting to come through.
The text was updated successfully, but these errors were encountered:
@josephwegner one thing I've done for this that works really well is to add a report link to the page which links to a new GitHub issue with the title/body/labels pre-formatted to file an issue.
The body of the issue would include the log of whatever caused the server to crash (and we don't need to show it on the error page, just a well designed error page and a link to report).
Right now we get a big ugly scary error page whenever the server crashes.
It seems like crashing will be a fairly normal thing for Pullup, so we should make this error page prettier. Here's the Heroku docs regarding the subject: https://devcenter.heroku.com/articles/error-pages
I also think we should have the log list on the error page, so that we can see clearer what caused the server to crash. That code is in a PR, waiting to come through.
The text was updated successfully, but these errors were encountered: