-
Notifications
You must be signed in to change notification settings - Fork 867
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
chore: bump gotestsum and fix flakey test causing nil channel send #2934
Conversation
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## master #2934 +/- ##
=======================================
Coverage 81.74% 81.74%
=======================================
Files 134 134
Lines 20367 20367
=======================================
Hits 16649 16649
Misses 2861 2861
Partials 857 857 ☔ View full report in Codecov by Sentry. |
99fd17e
to
8dff67d
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.
LGTM
Signed-off-by: zachaller <[email protected]>
So deferes are called in a last-in-first-out order this means, that we would close the channel before canceling the context which could lead to a nil pointer usage. Let's just manually control order. Signed-off-by: zachaller <[email protected]>
Signed-off-by: zachaller <[email protected]>
Signed-off-by: zachaller <[email protected]>
Signed-off-by: zachaller <[email protected]>
24c9e81
to
d770d5b
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
gotestsum now fails on nil pointers by default which is why this test issue is being fixed here as well
Change order of defer to prevent using closed channel
So deferes are called in a last-in-first-out order this means,
that we would close the channel before canceling the context which could
lead to a nil pointer usage. Let's just manually control order. We will also deregister the callbacks.