-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Write piped output periodically, rather than waiting for stdin to close #25
Conversation
Codecov Report
@@ Coverage Diff @@
## main #25 +/- ##
===================================================
+ Coverage 0.00000% 31.57895% +31.57895%
===================================================
Files 1 2 +1
Lines 74 76 +2
===================================================
+ Hits 0 24 +24
+ Misses 74 47 -27
- Partials 0 5 +5
Continue to review full report in Codecov by Sentry.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Tho not sure I understood what is the Mist interface we're implementing for for the incremental file updates
|
@thomshutt cool thanks for the explanation! I think the current implementation looks good for the use case while being simpler than handling background tickers or timers. |
During a livestream, Mist currently pipes updates to the manifest file continuously to the uploader binary but only closes the pipe once the stream is complete.
This means that we don't get a manifest file written until the stream finishes, which: