starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Include stack trace for unhandled exceptions on 500 responses and in job logs #11890

New Issue
Open
opened 2025-12-29 21:51:16 +01:00 by adam · 0 comments
adam commented 2025-12-29 21:51:16 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Dec 3, 2025).

NetBox version

v4.4.7

Feature type

Change to existing functionality

Proposed functionality

Currently, when dealing with an unhandled exception NetBox displays only the exception message. This FR proposes including the complete stack trace as well.

As the stack trace may be considered mildly sensitive due to the disclosure of file paths, we should sanitize file paths by omitting anything higher than the application's root path.

Use case

Stack traces are often necessary to expedite the troubleshooting process, and making these available to the user immediately is expected to simplify the bug reporting process for all parties.

Database changes

N/A

External dependencies

N/A

Originally created by @jeremystretch on GitHub (Dec 3, 2025). ### NetBox version v4.4.7 ### Feature type Change to existing functionality ### Proposed functionality Currently, when dealing with an unhandled exception NetBox displays only the exception message. This FR proposes including the complete stack trace as well. As the stack trace may be considered mildly sensitive due to the disclosure of file paths, we should sanitize file paths by omitting anything higher than the application's root path. ### Use case Stack traces are often necessary to expedite the troubleshooting process, and making these available to the user immediately is expected to simplify the bug reporting process for all parties. ### Database changes N/A ### External dependencies N/A
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label complexity: medium needs milestone netbox status: backlog type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#11890
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?