RCORE-2227 Updated non-streaming upload progress to report 1.0 if nothing to upload #7957
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.
What, How & Why?
Currently, the non-streaming upload progress callback notifications would report an estimate of 0.0 and the notification callback was being expired if the uploadable and uploaded values were reported as zero. Since the notification estimate is being expired, it make better sense to report the estimate of 1.0, since that suggests that the notification request is complete.
These changes update the notification callback invocation routine to report an estimate of 1.0 if the uploaded and uploadable values are 0. The original tests that checked for 0.0 were updated.
In addition, some of the tests were
SyncProgressNotifier::update()
with an estimates of 0.0 when the uploadable/uploaded or downloadable/downloaded values were zero. These calls were updated to provide an estimate of 1.0, since that mimics the actual behavior of the sync client progress reporting.Fixes #7952
☑️ ToDos
[ ] C-API, if public C++ API changed[ ]bindgen/spec.yml
, if public C++ API changed