-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
In Windows seems to fail to release lock on ls error #3633
Comments
@tkharris Thanks for reporting. We are going to try and get windows CI and testing set up in the next several weeks, these sorts of issues should get worked out soon. |
Got a windows VM running, managed to reproduce the issue. |
Hrm... We might need to update our locking dependency. Its been a solid year since I updated it. (June 21st, 2016) |
Hrm... there havent been any updates to that locking lib since our last update. It also supports windows via a fallback locking mechanism. I wonder if theres a better way to do locking on windows? |
Locking files is actually pretty easy on windows, they have mandatory file locks. Actually, it looks like there may be a stale PR you may be able to revive: camlistore/lock#2 (note, that's on the old repo). Unfortunately, the code in that PR looks a bit more complicated than it really should be... |
I made modifications to the lock library after encountering issues on a separate issue, those changes resolve this as well. They're currently under review. Once it passes, I'll create a PR to update the gx dep. |
Version information:
go-ipfs version: 0.4.4-
Repo version: 4
System version: amd64/windows
Golang version: go1.7
Type: Bug
Priority: P2
Description
In Windows seems to fail to release lock on ls error.
The text was updated successfully, but these errors were encountered: