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.
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
Client reports download status and download details #341
base: main
Are you sure you want to change the base?
Client reports download status and download details #341
Changes from 2 commits
0a8d819
6101559
9873c12
e69f28b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I am a bit worried that
status
is a struct owned by someone else and we modify it from our goroutine here, whilestatus
's other fields are also simultaneously being modified by the owner. If the code is accidentally modified in the future to modify the same fields we will have a problem.Can we instead change
updateFn
to accept theDownloadPercent
andDownloadBytesPerSecond
as parameters and eliminate thestatus
parameter fromdownloadReporter
? This way the responsibility for getting concurrency correctly will be sole responsibility of the caller ofdownloadReporter.report
instead of being a shared responsibility.Check failure on line 67 in client/internal/package_download_details_reporter.go
Check failure on line 67 in client/internal/package_download_details_reporter.go
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.
Is
reportStatuses
safe to be called concurrently? The docs don't say it, so I am not sure. Note thatreportStatuses
calls user-suppliedSetLastReportedStatuses
which also is not documented to be safe for concurrent call. If you look at the only implementation inInMemPackagesStore
I think it is indeed not safe to call concurrently.