support logPostStatus progress reporting #720
Merged
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
mason-fish
approved these changes
May 1, 2020
alfred-landrum
force-pushed
the
brim-log-progress
branch
from
eb2d34b
to
0b5bcfc
Compare
alfred-landrum
force-pushed
the
brim-log-progress
branch
from
0b5bcfc
to
a1db2d0
Compare
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.
If incoming LogPostStatus messages have the "log_total_bytes" field, use it & and the log_read_bytes field to update the progress bar. The log_total_bytes field is added by brimdata/zed#708 .
This is the UI side of #567 .