Properly use concurrent_transfers from MedusaConfig object #1244
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 this PR does:
This PR changes the default value to 0 (instead of 1). This way, the merging storage properties, the correct value wins.
This PR also makes sure that if we do end up with a 0, the medusa.ini ends up with a 1 because Medusa can't handle 0 concurrent transfers.
Which issue(s) this PR fixes:
Fixes #1239
Checklist