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

Add an option to turn off error handling #55

Open
kurin opened this issue Jul 31, 2018 · 0 comments
Open

Add an option to turn off error handling #55

kurin opened this issue Jul 31, 2018 · 0 comments

Comments

@kurin
Copy link
Owner

kurin commented Jul 31, 2018

By default, b2 retries forever on error, which is the behavior specified in the Backblaze integration checklist.

However, this often breaks users who expect a command either to succeed or to fail. For example, in restic/restic#1906 a user ran an interactive command which ought to have finished after a few seconds, either indicating success or printing an error to the effect of "Backblaze is unavailable."

Currently users can set context deadlines, but this only tells the user that a deadline exceeded, and there's no indication about whether they did something wrong or why the command didn't succeed.

An option to turn off error handling would cease all such retries. It could either be a ClientOption, which would disable error handling for every request from that client, or a context wrapper, which would allow users to disable error handling on a per-request basis.

@kurin kurin changed the title Add an option for turning off error handling Add an option to turn off error handling Jul 31, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant