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
Is your feature request related to a problem? Please describe.
When collecting a trace that is time range based it is possible that we have incomplete ranges. A range that starts but never finishes is rather common, but so is a range that shows an end, but there is no start.
It would be really nice if we could have a option in the conversion tool to include incomplete ranges. Ranges with no end should ideally be tagged/colored some way so that it is clear that the range did not complete.
I am not sure if there is anything we can do for ranges that didn't have a start, because the start event has all of the information about it (color, text, stream, etc). So there might be no way to insert it,
At a minimum when we do the conversion it would be great if we had a way to log when we see these and are throwing them out. Just so we know that it is happening, even if it does not show up in the nsys file.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When collecting a trace that is time range based it is possible that we have incomplete ranges. A range that starts but never finishes is rather common, but so is a range that shows an end, but there is no start.
It would be really nice if we could have a option in the conversion tool to include incomplete ranges. Ranges with no end should ideally be tagged/colored some way so that it is clear that the range did not complete.
I am not sure if there is anything we can do for ranges that didn't have a start, because the start event has all of the information about it (color, text, stream, etc). So there might be no way to insert it,
At a minimum when we do the conversion it would be great if we had a way to log when we see these and are throwing them out. Just so we know that it is happening, even if it does not show up in the nsys file.
The text was updated successfully, but these errors were encountered: