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

feat(mount): don't give up on error #146

Merged
merged 1 commit into from
Mar 28, 2020
Merged

feat(mount): don't give up on error #146

merged 1 commit into from
Mar 28, 2020

Conversation

Stebalien
Copy link
Member

Instead of giving up when a single datastore fails, operate on all datastores first. That way:

  • If one datastore doesn't support disk usage, we can at least return our best estimate for the ones that do.
  • If one datastore fails to sync, we won't fail to sync the others.
  • If one datastore refuses to close, we'll close the others.

Etc.

Also:

  • Drop xerrors. We already need go 1.13 elsewhere.
  • Use uber's multierr. It's much simpler than hashicorps (and is already a dependency through zap, fx, etc.).

Instead of giving up when a single datastore fails, operate on all datastores
first. That way:

* If one datastore doesn't support disk usage, we can at least return our best
  estimate for the ones that do.
* If one datastore fails to sync, we won't fail to sync the others.
* If one datastore refuses to close, we'll close the others.

Etc.

Also:

* Drop xerrors. We already need go 1.13 elsewhere.
* Use uber's multierr. It's much simpler than hashicorps (and is already a
  dependency through zap, fx, etc.).
@Stebalien Stebalien merged commit 6bee6a4 into master Mar 28, 2020
@Stebalien Stebalien deleted the feat/try-harder branch March 28, 2020 05:58
@aschmahmann aschmahmann mentioned this pull request Sep 22, 2020
72 tasks
@Stebalien Stebalien mentioned this pull request May 11, 2021
27 tasks
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.

1 participant