-
Notifications
You must be signed in to change notification settings - Fork 119
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
#824 Automatically convert -1 in maximum-test-shards to the maximum shard amount #825
#824 Automatically convert -1 in maximum-test-shards to the maximum shard amount #825
Conversation
Codecov Report
@@ Coverage Diff @@
## master #825 +/- ##
============================================
+ Coverage 80.02% 80.11% +0.08%
Complexity 674 674
============================================
Files 151 151
Lines 3084 3087 +3
Branches 442 443 +1
============================================
+ Hits 2468 2473 +5
+ Misses 337 336 -1
+ Partials 279 278 -1 |
c9df66d
to
3c78771
Compare
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 think this implementations stands between two solutions and we should decide which way to proceed.
@bootstraponline I don't know if this is desired behavior but I think we should either 'fix' all incorrect input values or throw an error for all.
With this implementation we treat -1
with special care but how about 0
, < -1
and > 50
.
We could change input to the closest acceptable value and maybe print message to inform use that incorrect input was provided and how flank process it...
WDYT?
|
I understand, thanks for response! |
Set 1..50 range to use AVAILABLE_SHARD_COUNT_RANGE to avoid test fails on incerase range
…e name to convertToShardCount
4618476
to
966bec7
Compare
Fixes #824
Checklist