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

Wrong SVG visualization with multiple path in Circuits Terminations #7355

New Issue
Closed
opened 2025-12-29 20:22:14 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:22:14 +01:00
Owner
Copy Link

Originally created by @renatoalmeidaoliveira on GitHub (Dec 15, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.3.10

Python version

3.8

Steps to Reproduce

  1. Create a Circuit (Multi-Root)
  2. Create a Circuit (Multi-100)
  3. Create a Circuit (Multi-200)
  4. Create on each Circuit a termination in the same site, and connect Multi-100 and Multi-200 to Multi-Root
  5. Connect the other Circuit termination to some device interface

Expected Behavior

When you render the connection trace in the interface connected to the Multi-Root all other circuits and device interfaces are show in the svg

Observed Behavior

Trace from the interface connected to the Multi-Root Circuit:

image

Trace from the interface connected to the Multi-100 Circuit:

image

Trace from the interface connected to the Multi-200 Circuit:

image

Originally created by @renatoalmeidaoliveira on GitHub (Dec 15, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.3.10 ### Python version 3.8 ### Steps to Reproduce 1. Create a Circuit (Multi-Root) 2. Create a Circuit (Multi-100) 3. Create a Circuit (Multi-200) 4. Create on each Circuit a termination in the same site, and connect Multi-100 and Multi-200 to Multi-Root 5. Connect the other Circuit termination to some device interface ### Expected Behavior When you render the connection trace in the interface connected to the Multi-Root all other circuits and device interfaces are show in the svg ### Observed Behavior # Trace from the interface connected to the Multi-Root Circuit: ![image](https://user-images.githubusercontent.com/16046203/207743493-e57def12-d47a-4b71-97f0-b8d98db57745.png) # Trace from the interface connected to the Multi-100 Circuit: ![image](https://user-images.githubusercontent.com/16046203/207743580-794adde8-ca00-41ac-b3d2-9a72b82b9da3.png) # Trace from the interface connected to the Multi-200 Circuit: ![image](https://user-images.githubusercontent.com/16046203/207743663-6f1e96fa-22e9-4655-a671-f72175363d9a.png)
adam added the type: bugstatus: accepted labels 2025-12-29 20:22:14 +01:00
adam closed this issue 2025-12-29 20:22:15 +01:00
adam commented 2025-12-29 20:22:16 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 15, 2022):

  1. Create on each Circuit a termination in the same site, and connect Multi-100 and Multi-200 to Multi-Root

Please expand on this, as it's not clear exactly what connections are to be made.

@jeremystretch commented on GitHub (Dec 15, 2022): > 4. Create on each Circuit a termination in the same site, and connect Multi-100 and Multi-200 to Multi-Root Please expand on this, as it's not clear exactly what connections are to be made.
adam commented 2025-12-29 20:22:16 +01:00
Author
Owner
Copy Link

@renatoalmeidaoliveira commented on GitHub (Dec 15, 2022):

@jeremystretch
1 - For all Circuits create Termination A on the same site.
2 - In the Circuit Multi-Root go in Termination A and click in connect and choose Circuit Termination
3 - In the Side B, add the Side B termination of the other Circuits (Multi-100 and Multi-200)

@renatoalmeidaoliveira commented on GitHub (Dec 15, 2022): @jeremystretch 1 - For all Circuits create Termination A on the same site. 2 - In the Circuit Multi-Root go in Termination A and click in connect and choose Circuit Termination 3 - In the Side B, add the Side B termination of the other Circuits (Multi-100 and Multi-200)
adam commented 2025-12-29 20:22:16 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 16, 2022):

When you render the connection trace in the interface connected to the Multi-Root all other circuits and device interfaces are show in the svg

We can only render cable paths up to the point where there's a divergent split, which in this case is the two far-end circuit terminations. The correct behavior should be to convey that the path splits and give the user the option of choosing one branch to follow. Here's what I've implemented:

Screenshot 2022-12-16 at 16-27-29 Cable Trace for Interface GigabitEthernet0_1_2 NetBox

@jeremystretch commented on GitHub (Dec 16, 2022): > When you render the connection trace in the interface connected to the Multi-Root all other circuits and device interfaces are show in the svg We can only render cable paths up to the point where there's a divergent split, which in this case is the two far-end circuit terminations. The correct behavior should be to convey that the path splits and give the user the option of choosing one branch to follow. Here's what I've implemented: ![Screenshot 2022-12-16 at 16-27-29 Cable Trace for Interface GigabitEthernet0_1_2 NetBox](https://user-images.githubusercontent.com/13487278/208191903-d84f1ab1-23da-4a25-af73-9c706381bc40.png)
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 status: accepted type: bug
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#7355
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?