-
Notifications
You must be signed in to change notification settings - Fork 135
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
Tink Server: Fix runtime panic #536
Tink Server: Fix runtime panic #536
Conversation
…ady set and may not be reset The grpc server interceptors need to be chained to not cause a runtime panic. Signed-off-by: Jacob Weinstock <[email protected]>
Codecov Report
@@ Coverage Diff @@
## master #536 +/- ##
==========================================
+ Coverage 33.59% 33.61% +0.01%
==========================================
Files 44 44
Lines 3387 3385 -2
==========================================
Hits 1138 1138
+ Misses 2152 2150 -2
Partials 97 97
Continue to review full report at Codecov.
|
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 there a test we can add that would have caught this?
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.
Whooooops. I didn't even notice that and am surprised the compiler didn't!
I should have started up the tink stack before submitting the PR. I'll get my rig set up before I dig in more (tink-worker and tink need some more otel bits). Ideally we can come up with a functional test that lets us exercise the tink binaries a ilttle without bringing up the whole thing. |
Description
Fix runtime
panic: The unary server interceptor was already set and may not be reset
The grpc server interceptors need to be chained to not cause a runtime panic.
Why is this needed
Fixes: #535
How Has This Been Tested?
make test
make run
docker logs tink_tinkerbell_1
- validate the server started up successfully.How are existing users impacted? What migration steps/scripts do we need?
Checklist:
I have: