handle sample rate type incompatibilities#2036
Conversation
fdeca99 to
00bfdf1
Compare
st0012
left a comment
There was a problem hiding this comment.
Thanks for raising the issue. I think in the case of configurations, we should raise errors to explicitly warn users about unexpected values.
|
This pull request has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #2036 +/- ##
==========================================
+ Coverage 83.19% 83.21% +0.02%
==========================================
Files 119 119
Lines 5653 5661 +8
==========================================
+ Hits 4703 4711 +8
Misses 950 950
☔ View full report in Codecov by Sentry. |
st0012
left a comment
There was a problem hiding this comment.
This will result in Configuration#trace_sample_rate == 0.0.
I was a bit confused by this statement. Is that still true after your change?
It is no longer true, I've now updated the description. |
|
This looks good now. Can you add a changelog entry for it? Thx |
Co-authored-by: Stan Lo <stan001212@gmail.com>
Co-authored-by: Stan Lo <stan001212@gmail.com>
2aaf83c to
0d99b2f
Compare
Description
The suggested workaround in #2035 results in an
ArgumentError, since we aren't casting toFloat. This PR will allow us to fail earlier and with a more specific error message.