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
Use case
I want to debug with clarity and knowing what to expect.
Feature
What would help?
A debug session with multiple debug results should be clear on which one happened first
Right now they are not in chronological order in any way, the timings are as follows:
Nr. 1: 17-06-24 13:09:31:693
Nr. 2: 17-06-24 13:09:03:607
Nr. 3: 17-06-24 13:09:14:192
It would be great that these are either chronologically ordered, or to see the time stamp of each session.
Sometimes a situation happens that you would like to know what debug sessions are available and preferably be able to turn some on or off. Situations are:
You do not know whether the debug session is still going to appear or whether it is already closed.
Lost track of when the debug session started (and deleted the history in the terminal)
This can result into either into:
Long uncertain wait times
Starting another debug session so you receive multiple windows of the same session.
So something like an overview of active debug sessions would be great.
And it would be even better if you can also close some debug sessions in case you started 2 for the same proxy accidently for example.
Thank you very much!
The text was updated successfully, but these errors were encountered:
Use case
I want to debug with clarity and knowing what to expect.
Feature
What would help?
Right now they are not in chronological order in any way, the timings are as follows:
Nr. 1: 17-06-24 13:09:31:693
Nr. 2: 17-06-24 13:09:03:607
Nr. 3: 17-06-24 13:09:14:192
It would be great that these are either chronologically ordered, or to see the time stamp of each session.
This can result into either into:
So something like an overview of active debug sessions would be great.
And it would be even better if you can also close some debug sessions in case you started 2 for the same proxy accidently for example.
Thank you very much!
The text was updated successfully, but these errors were encountered: