trying to debug permissions failure #1276
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
whyrusleeping
force-pushed
the
debug/perm-fail
branch
5 times, most recently
from
24f9de8
to
cc90553
Compare
This was referenced May 22, 2015
| @@ -13,6 +16,10 @@ import ( | |||
| // TODO rename repo lock and hide name | |||
| const LockFile = "repo.lock" | |||
|
|
|||
| func errPerm(path string) error { | |||
| return fmt.Errorf("failed to take lock at %s: permission denied", path) | |||
There was a problem hiding this comment.
maybe:
"locking %s: permission denied"
so that the error prints as:
Error: locking <path>: permission denied.
(but maybe this is fine)
jbenet
added a commit
that referenced
this pull request
May 22, 2015
trying to debug permissions failure
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I beleive that i've solved the permissions error in t0020-init.sh
the Lock function arbitrarily returns a different error that doesnt mean what you expect it to.
this has been run quite a four times with no repro of the issue, assuming its fixed