provider network cable trace UI bug

Deployment Type

Self-hosted

NetBox Version

v.4.0.8

Python Version

3.12

Steps to Reproduce

Create a device
Create an interface for that device
Create a circuit
Connect the interface to the circuit (Z side)
Create a provider network
Connect the provide network to the circuit (A side)
Do a cable trace for the above circuit 

Easy visual example here: : https://demo.netbox.dev/circuits/circuit-terminations/15/trace/

Expected Behavior

When running a cable trace on a circuit that is connected to a provider network, shouldn't the dotted line that connects Termination A actually 'connect' to the Level3 MPLS provider network? Is the large gap there supposed to be there? It's present in the demo site so I'm not sure if this is by design. (pardon my poor mspaint skills)

Observed Behavior

[arthanson]

Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

Please notice in the bug report form: "Additionally, do not rely on the demo instance for reproducing suspected bugs, as its data is prone to modification or deletion at any time."

apologies, I've updated the report to include the exact steps to generate the visual pictures included.

[github-actions]

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.