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.

Sign up for GitHub

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

Jump to bottom

Middleware to intercept server errors related to installation issues #1683

Closed
jeremystretch opened this issue Nov 2, 2017 · 1 comment
Closed

Middleware to intercept server errors related to installation issues #1683

jeremystretch opened this issue Nov 2, 2017 · 1 comment
Labels
type: feature Introduction of new functionality to the application

Comments

@jeremystretch
Copy link
Member

Issue type

[x] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version: 3.5.2
  • NetBox version: 2.2.4

Description

It may be worthwhile to implement a lightweight middleware to intercept common exceptions related to installation issues. For example, a ProgrammingError typically indicates that database migrations have not been applied following an upgrade. Returning hints at possible solutions to the user would help shorten the support cycle and cut down on invalid bug reports.
@jeremystretch jeremystretch added the type: feature Introduction of new functionality to the application label Nov 2, 2017
@lampwins
Copy link
Contributor

lampwins commented Nov 2, 2017

I think you are on the right track. I have seem somewhat similar things done with https://docs.djangoproject.com/en/1.11/topics/http/middleware/#process-exception

@jeremystretch jeremystretch mentioned this issue Nov 14, 2017
Merged
@lock lock bot locked as resolved and limited conversation to collaborators Jan 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
type: feature Introduction of new functionality to the application
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lampwins @jeremystretch