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

Feed Connection Error Not Handled #8705

New Issue
Closed
opened 2025-12-29 20:40:09 +01:00 by adam · 8 comments
adam commented 2025-12-29 20:40:09 +01:00
Owner
Copy Link

Originally created by @adhoniran on GitHub (Oct 3, 2023).

NetBox version

v3.6.3

Python version

3.11

Steps to Reproduce

  1. Opening NetBox application while server don't have Internet connection or DNS resolution don't works.

Expected Behavior

NetBox displaying a graceful notification on feed widget informing a getting feed problem

Observed Behavior

NetBox is displaying a unhandled notification

Originally created by @adhoniran on GitHub (Oct 3, 2023). ### NetBox version v3.6.3 ### Python version 3.11 ### Steps to Reproduce 1. Opening NetBox application while server don't have Internet connection or DNS resolution don't works. ### Expected Behavior NetBox displaying a graceful notification on feed widget informing a getting feed problem ### Observed Behavior NetBox is displaying a unhandled notification
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 20:40:09 +01:00
adam closed this issue 2025-12-29 20:40:09 +01:00
adam commented 2025-12-29 20:40:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 3, 2023):

Opening NetBox application while server don't have Internet connection or DNS resolution don't works.

After viewing what page? If the dashboard, how do you have it configured? Please provide more detail.

NetBox is displaying a unhandled notification

What specifically are you seeing?

@jeremystretch commented on GitHub (Oct 3, 2023): > Opening NetBox application while server don't have Internet connection or DNS resolution don't works. After viewing what page? If the dashboard, how do you have it configured? Please provide more detail. > NetBox is displaying a unhandled notification What specifically are you seeing?
adam commented 2025-12-29 20:40:10 +01:00
Author
Owner
Copy Link

@adhoniran commented on GitHub (Oct 3, 2023):

It's in the main page, before login included...
I just attached some screenshots:

feed-conf

feed-error

@adhoniran commented on GitHub (Oct 3, 2023): It's in the main page, before login included... I just attached some screenshots: ![feed-conf](https://github.com/netbox-community/netbox/assets/13842906/51c97452-d303-4160-98ec-5fccddf95e4c) ![feed-error](https://github.com/netbox-community/netbox/assets/13842906/fe7e9289-9ed6-4ab7-9224-61b4807ddaf2)
adam commented 2025-12-29 20:40:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 3, 2023):

@adhoniran I'm afraid the screenshots aren't showing. Could you try to upload them via GitHub's web interface?

@jeremystretch commented on GitHub (Oct 3, 2023): @adhoniran I'm afraid the screenshots aren't showing. Could you try to upload them via GitHub's web interface?
adam commented 2025-12-29 20:40:10 +01:00
Author
Owner
Copy Link

@adhoniran commented on GitHub (Oct 3, 2023):

Files added again...

feed-conf

feed-error

@adhoniran commented on GitHub (Oct 3, 2023): Files added again... ![feed-conf](https://github.com/netbox-community/netbox/assets/13842906/4be06ad0-15e4-439f-8a28-2cfe425c5a75) ![feed-error](https://github.com/netbox-community/netbox/assets/13842906/fea3be11-bbb5-40ff-b81d-78830146487a)
adam commented 2025-12-29 20:40:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 5, 2023):

I've reclassified this as a feature request, as upon further consideration I don't believe the error message can be considered as a bug. The exception is not unhandled as the original issue suggests; rather the error message is simply presented in its raw form to the user.

@jeremystretch commented on GitHub (Oct 5, 2023): I've reclassified this as a feature request, as upon further consideration I don't believe the error message can be considered as a bug. The exception is not unhandled as the original issue suggests; rather the error message is simply presented in its raw form to the user.
adam commented 2025-12-29 20:40:10 +01:00
Author
Owner
Copy Link

@adhoniran commented on GitHub (Oct 13, 2023):

I agree about the feature request classification, I can treat the main error reasons and write a code proposal.

@adhoniran commented on GitHub (Oct 13, 2023): I agree about the feature request classification, I can treat the main error reasons and write a code proposal.
adam commented 2025-12-29 20:40:11 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 27, 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 (Mar 27, 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).
adam commented 2025-12-29 20:40:11 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 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 (May 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.
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 pending closure status: needs owner 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#8705
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?