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
The original design assumed that pushbuffers would eventually finish. However, in reality, the pushbuffers typically never stop running, as there's always new data queued already.
I then decided to implement continous tracing (which is also more useful), but the old stop logic remains.
I'm not sure which changes would be necessary to detect a restart.
I worry that this might break our current tracing logic. Also see #7
The text was updated successfully, but these errors were encountered:
JayFoxRox
changed the title
Don't stop if trace is finished
Don't stop if pushbuffer is finished
Jun 27, 2018
The original design assumed that pushbuffers would eventually finish. However, in reality, the pushbuffers typically never stop running, as there's always new data queued already.
I then decided to implement continous tracing (which is also more useful), but the old stop logic remains.
I'm not sure which changes would be necessary to detect a restart.
I worry that this might break our current tracing logic. Also see #7
The text was updated successfully, but these errors were encountered: