-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Aditional Data in Script Errors #13732
Comments
Being able to see the traceback more easily would be a great enhancement. |
Blocked by #14438 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide. |
This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary. |
NetBox version
v3.6.1
Feature type
Change to existing functionality
Proposed functionality
Add Script input data along with the error stack trace when a script fails
Use case
When you have a script with multiple input variables, and are maintained by different teams it's useful to know what were the script inputs to correctly troubleshoot the error.
Database changes
None
External dependencies
None
The text was updated successfully, but these errors were encountered: