-
Notifications
You must be signed in to change notification settings - Fork 44
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
Avoid a partially nil host
as sink in test muxed providers
#2699
Conversation
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.
Is this another nil interface problem? 😢
Glad to see this is only a problem with tests.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2699 +/- ##
==========================================
- Coverage 69.46% 69.46% -0.01%
==========================================
Files 301 301
Lines 38637 38644 +7
==========================================
+ Hits 26841 26845 +4
- Misses 10273 10275 +2
- Partials 1523 1524 +1 ☔ View full report in Codecov by Sentry. |
0fa1f8d
to
03503f7
Compare
Yes 😞 |
I've added a test and am merging now. I'll run tests for another bridge release as soon as this goes in. |
This change prevents test providers from being initialized with partially nil logging sinks, which panicked in tests. Happily, the problem is restricted to `MakeMuxedServer`, a testing API. This was never present in production code. Fixes #2697 --- This is [my least favorite go feature](https://www.iwahbe.com/blog/go-pointers-considered-confusing/).
03503f7
to
17f803f
Compare
This PR has been shipped in release v3.97.0. |
This change prevents test providers from being initialized with partially nil logging sinks, which panicked in tests. Happily, the problem is restricted to
MakeMuxedServer
, a testing API. This was never present in production code.Fixes #2697