You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently cannot start a trace server without opening a trace. My understanding is that we want to search available TraceServerContributors for one where the trace being attempted to open is already available.
It would be simpler to have the functionality of opening a trace and starting a trace-server de-coupled. The functionality of starting a trace-server without the need of a file path would be invaluble.
My understanding and suggested solution:
Instead of having one current route for starting a server:
Start Trace Server with mandatory file path
We could have three options:
Start Trace Server with optional file path, searching available TraceServerContributors for one with the trace open (previous implementation).
Start ANY trace server from ANY TraceServerContributor (if any)
Open a trace with a current and available TraceServerContributor.
The text was updated successfully, but these errors were encountered:
We currently cannot start a trace server without opening a trace. My understanding is that we want to search available
TraceServerContributor
s for one where the trace being attempted to open is already available.It would be simpler to have the functionality of opening a trace and starting a trace-server de-coupled. The functionality of starting a trace-server without the need of a file path would be invaluble.
My understanding and suggested solution:
Instead of having one current route for starting a server:
We could have three options:
TraceServerContributor
s for one with the trace open (previous implementation).TraceServerContributor
(if any)TraceServerContributor
.The text was updated successfully, but these errors were encountered: