Instant Warping
Categories
(Core Graveyard :: Web Replay, enhancement, P5)
Tracking
(Not tracked)
People
(Reporter: bhackett1024, Unassigned)
References
Details
Similarly to instant stepping, if we know the possible time warp targets then we could eagerly generate the information at time warp targets, so that if a user warps to a console message or error then we could update the UI immediately, before a replaying process has reached that point. Unlike stepping, it might take a little while for a replaying process to reach the warp target and allow deeper queries about the program state there (evaluations and so forth). With many replaying children in a cloud based setup, this will be faster, though it's hard to put a bound on how long it will take to reach an arbitrary execution point in an arbitrary recording.
Reporter | ||
Updated•6 years ago
|
Comment 1•6 years ago
|
||
The priority flag is not set for this bug.
:bhackett, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•6 years ago
|
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Comment 2•6 years ago
|
||
I'm folding this into bug 1556813.
Updated•5 years ago
|
Description
•