Add a history stream for apply ticks / views updates #177
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
`base.system.createApplyTickHistoryStream()` emits once per `apply` tick
with an object of the form:
```
{
index: Number, // the index of the 'info' block in the `system.db`
views: [{ key, appends }], // A list of changed views with the number of blocks appended
writer: { key, length } // Which writer appended the blocks and what its new length is
}
```
This can be used for debugging how the apply function changed views over
the history of the autobase system.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
base.system.createApplyTickHistoryStream()emits once perapplytick with an object of the form:This was prompted by my need to track what writer blocks / batches update the autobase's view(s). @mafintosh suggested it could be a nice API used for debugging as well.