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.

Sign up for GitHub

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

Jump to bottom

Excon errors should not be leaked upwards #162

Open
kke opened this issue Sep 4, 2019 · 0 comments · May be fixed by #163
Open

Excon errors should not be leaked upwards #162

kke opened this issue Sep 4, 2019 · 0 comments · May be fixed by #163
Assignees
@kke
Labels
chore

Comments

@kke
Copy link
Contributor

kke commented Sep 4, 2019 •
edited
Loading

User should not have to rescue Excon::Error, Excon::Error::Socket, Excon::Error::Certificate etc when using k8s-client.
@kke kke added the chore label Sep 4, 2019
@kke kke self-assigned this Sep 4, 2019
@kke kke linked a pull request Sep 4, 2019 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kke kke

Labels
chore
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Reraise Excon errors as K8s::Errors kontena/k8s-client
1 participant
@kke