-
Notifications
You must be signed in to change notification settings - Fork 784
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
SPRING_SLEUTH_SAMPLER_PERCENTAGE is not a percentage #397
Comments
Since percents as their name suggests are values divided by 100 you can also represent them as a double ( 80% == 80/100 == 0.8). We've decided to go with the double representation :) But English is not my native language so maybe we've used a wrong name for the property. @adriancole WDYT? |
Maybe threshold is a better term for a 0-1 function? On 11 Sep 2016 14:17, "Marcin Grzejszczak" notifications@github.com wrote:
|
I think threshold means something else. |
SGTM! thanks, chris On Mon, Sep 12, 2016 at 11:22 AM, Chris Richardson <notifications@github.com
|
This is a breaking change actually (which I don't like to do). We could allow people to provide entries greater > 0. You could then provide
or
and that would be the same. I could also provide a new property for version 1.1 and deprecate the old one (but not remove it). I could remove it for 1.2 or sth like that. WDYT? |
ping @cer ? |
SGTM |
What if you actually wanted 0.5% (not completely unlikely)? I think it might be better that we just live with it and document the mistake. Or else introduce a new notation with "%" in it or something (seems like overkill for such a simple thing). |
without this change the percentage value might have been set to over 1.0 with this change we explain what are the valid values and what are the reasons for keeping the value as it is fixes #397
Isn't a percentage between 0 and 100%?
The text was updated successfully, but these errors were encountered: