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

server: Ignore NotConnected errors on shutdown #654

Closed
wants to merge 2 commits into from

Conversation

LucioFranco
Copy link
Member

Related to hyperium/tonic#1183

I started to see this error come up when debugging the above tonic issue, to me ignoring this error seems okay in this context, but I'd like to have some other eyes on it.

cc @seanmonstar @hawkw

Copy link
Collaborator

@hawkw hawkw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think it seems fine to ignore the error in this case. the idea of completely ignoring an error makes me mildly uncomfortable, so maybe we should be logging it? otherwise, lgtm.

src/proto/connection.rs Outdated Show resolved Hide resolved
src/proto/connection.rs Outdated Show resolved Hide resolved
@seanmonstar
Copy link
Member

I'm not so sure we should choose to ignore the error. We don't know the full context of the IO transport. It feels more correct to me to pass that error along to the user, and they can decide if to ignore it or not.

Co-authored-by: Eliza Weisman <eliza@buoyant.io>
@flumm
Copy link

flumm commented Jan 9, 2023

seems to be more or less the same changes i proposed in #653

Copy link
Member

@seanmonstar seanmonstar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My concern still exists

@LucioFranco
Copy link
Member Author

I'm not so sure we should choose to ignore the error. We don't know the full context of the IO transport. It feels more correct to me to pass that error along to the user, and they can decide if to ignore it or not.

Sounds good to me

@LucioFranco LucioFranco closed this Jan 9, 2023
@LucioFranco LucioFranco deleted the lucio/fix-not-connected-server branch January 9, 2023 17:46
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

Successfully merging this pull request may close these issues.

4 participants