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

Do not restore sockets, correct error handling #1731

Merged
merged 1 commit into from
Apr 20, 2018
Merged

Do not restore sockets, correct error handling #1731

merged 1 commit into from
Apr 20, 2018

Conversation

fd0
Copy link
Member

@fd0 fd0 commented Apr 20, 2018

Closes #1730

@codecov-io
Copy link

codecov-io commented Apr 20, 2018

Codecov Report

Merging #1731 into master will decrease coverage by 0.11%.
The diff coverage is 0%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1731      +/-   ##
==========================================
- Coverage    52.1%   51.99%   -0.12%     
==========================================
  Files         148      148              
  Lines       11712    11718       +6     
==========================================
- Hits         6103     6093      -10     
- Misses       4658     4678      +20     
+ Partials      951      947       -4
Impacted Files Coverage Δ
internal/restic/restorer.go 51.8% <0%> (-4.04%) ⬇️
internal/checker/checker.go 64.59% <0%> (-3.91%) ⬇️
internal/archiver/archiver.go 64.25% <0%> (+0.21%) ⬆️
cmd/restic/global.go 29.15% <0%> (+0.87%) ⬆️
internal/backend/rclone/backend.go 72.25% <0%> (+1.93%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a9c2e84...09bd924. Read the comment docs.

@@ -76,6 +76,11 @@ func (res *Restorer) restoreTo(ctx context.Context, target, location string, tre
continue
}

// sockets cannot be restored
if node.Type == "socket" {
Copy link
Contributor

Choose a reason for hiding this comment

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

should backup skip sockets too?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yep, I've just commit this (locally) to the new-archiver branch :)

@fd0 fd0 merged commit 09bd924 into master Apr 20, 2018
fd0 added a commit that referenced this pull request Apr 20, 2018
Do not restore sockets, correct error handling
@fd0 fd0 deleted the fix-1730 branch April 20, 2018 12:23
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.

3 participants