Catch assertions in cable path generation and display a user-friendly error #8739

Closed
opened 2025-12-29 20:40:37 +01:00 by adam · 5 comments
Owner

Originally created by @DanSheps on GitHub (Oct 11, 2023).

Proposed Changes

  1. Provide meaningful errors for each assert
  2. Catch assertions in the edit views when generating cable paths and return a user-friendly message
  3. (Optional) Provide a list of unsupported connections in the documents or as part of the error

Justification

Currently, when an assert is generated, we receive the default Django exception page. This would clean up the error while still providing good user feedback.

Originally created by @DanSheps on GitHub (Oct 11, 2023). ### Proposed Changes 1. Provide meaningful errors for each assert 2. Catch assertions in the edit views when generating cable paths and return a user-friendly message 3. (Optional) Provide a list of unsupported connections in the documents or as part of the error ### Justification Currently, when an assert is generated, we receive the default Django exception page. This would clean up the error while still providing good user feedback.
adam added the status: under reviewtype: housekeepingnetbox labels 2025-12-29 20:40:37 +01:00
adam closed this issue 2025-12-29 20:40:37 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 10, 2024):

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.

@github-actions[bot] commented on GitHub (Jan 10, 2024): 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](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (May 15, 2024):

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.

@github-actions[bot] commented on GitHub (May 15, 2024): 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](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (Jun 15, 2024):

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.

@github-actions[bot] commented on GitHub (Jun 15, 2024): 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.
Author
Owner

@DanSheps commented on GitHub (Jun 18, 2024):

The error message portion is being fixed under #15016 however we should do something about the third item (documentation)

@DanSheps commented on GitHub (Jun 18, 2024): The error message portion is being fixed under #15016 however we should do something about the third item (documentation)
Author
Owner

@github-actions[bot] commented on GitHub (Sep 16, 2024):

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.

@github-actions[bot] commented on GitHub (Sep 16, 2024): 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](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8739