-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Upgraded Fuse emits CLI warning OSX, fails to mount with error #2650
Comments
i also get this warning but i have
|
I, too, am getting these errors on Initially the error is:
I ran
After running
I also tried running Checking the config file I do see the following line added:
And when removed, I again get the original I'm on OSX 10.9.5. I've reproduced it on ipfs versions |
Okay so I got kinda tired of this and looked into it. According to mount_darwin.go, the config value expected to be attached to Therefore one cannot set it to the correct value by only using |
@whyrusleeping this should fix one part of the issue, which is the confusing config behavior, but the actual problem is that Go's I'll test your patch and look into this more in couple hours. |
@paulsnar ah, in the comment you link to, there is an error printed rather sneakily at the end saying:
That looks to me like it tried to install fuse-version itself and failed on the go get for the stated reason, but it shouldnt have gotten that far anyways, i'm left wondering what the error returned by if _, err := exec.LookPath("fuse-version"); err == nil {
return nil // got it!
} else {
log.Error("LookPath error: ", err)
} recompiling, and seeing what it prints? |
This may be out of scope of this particular issue but with regard to |
Can you show us an output of |
@Kubuxu Actually, upon second check, my
|
I also saw this issue in OSX 10.11.6 ipfs 0.4.4 |
Installed stable fuse 2.8.3. CLI warns:
I don't believe an installation of go should be a prerequisite for the check since I have installed an ipfs binary.
The key and value appear to have been added regardless (excerpt of
~/.ipfs/config
below):Regardless, this results in an invalid key:
The text was updated successfully, but these errors were encountered: