Repository navigation
Fix state transfer rate before the bar starts - #240
Merged
Merged
Conversation
Owner
|
Thanks!! Looks good |
This file contains hidden or 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
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.
Before the first update,
New64(100).State()computes the transfer rate as0/0, producingNaN. This makes the state impossible to encode as JSON, and the/statehandler created byStartHTTPServerreturns an empty body.Leave the rate at zero until positive elapsed time is available. Add regressions for unstarted known-length, unknown-length, and resumed bars, their transition to a positive rate, and an actual initial
/staterequest.Validation: full
go test -race -cover -vet=off .on Go 1.25.13 and 1.26.6;go vet .;go mod tidy -diff;go build ./.... The three initial-state cases and HTTP regression fail before the fix and pass afterward.