Skip to content
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

couple of panics in the library #12

Closed
jessfraz opened this issue Sep 12, 2021 · 2 comments
Closed

couple of panics in the library #12

jessfraz opened this issue Sep 12, 2021 · 2 comments

Comments

@jessfraz
Copy link

here is an example: https://github.com/oxidecomputer/steno/blob/main/src/sec.rs#L265

Can I make a PR to change these to errors? or maybe log a warning? just don't want my whole server to panic when it occurs.

I am getting one of them quite a few times, unsure if this is valuable data

Screen Shot 2021-09-12 at 8 42 02 AM

@davepacheco
Copy link
Collaborator

Sorry for the trouble. There's a bunch of discussion on the various cases we panic (including the one you mentioned) in #16. From my understanding, you'd hit these today only after you hit an internal bug in Steno from which we cannot recover. I don't see that in your screenshot -- I only see the follow-on panics. It'd be good to get that first problem understood.

Given that we've hit an unrecoverable error, we panic any time you try to use the SecClient again. We do that because Nexus is probably going to want to do that. We could in principle return an error instead, but what is your program trying to do when it's calling shutdown? What would you do with an error at that point that means that all future calls to the SecClient will produce that error, too?

@davepacheco
Copy link
Collaborator

I don't think there's enough information here to root-cause the initial problem. #32 covers avoiding panicking on consumer misuse. I'm not sure if trying to use the SEC object after shutting it down would count.

@davepacheco davepacheco closed this as not planned Won't fix, can't repro, duplicate, stale Jul 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants