Improve error when invoking IPFS concurrently

[Stebalien]

Currently, we return "resource temporarily unavailable" which is the underlying error returned when we fail to lock the repo. However, that doesn't tell the user what's going on.

We should replace that error with "IPFS currently running", or something like that.

[utkarsh5k]

Looking to get involved with this project. I can pick this up.

[Stebalien]

Awesome! I believe the correct way to fix this is to modify the Lock function in github.com/ipfs/go-fs-lock to inspect the error. Really, this should probably move some of the error handling code from the Locked function into the Lock function.

[mahekchheda]

Is this still up for grabs? I would like to start contributing to this project from this.

[Stebalien]

@mahekchheda yes! The code you're looking for is here: https://github.com/ipfs/go-fs-lock/blob/5ab4a142bd9022c9ee4130c9c83fdca06f9acf9c/fslock.go#L23-L71

[leiter-jakab]

Hi, I created a pull request for this issue ipfs/go-fs-lock#9. I would be glad to hear your feedback. Unfortunately I didn't manage to link up the commits with this issue, because it's in a different repository.

[leiter-jakab]

@Stebalien I think this issue has been solved with ipfs/go-fs-lock#9.