codenotary / immudb

immudb - immutable database based on zero trust, SQL/Key-Value/Document model, tamperproof, data change history
https://immudb.io
Other
8.55k stars 343 forks source link

The process cannot access the file because another process has locked a portion of the file #733

Closed rzamoramx closed 3 years ago

rzamoramx commented 3 years ago

What happened

I'm been trying to create a verified data using the VerifiedSet method of the Go library, but I'm got an error: "The process cannot access the file because another process has locked a portion of the file"

What you expected to happen

A normal entry done

Environment Go 1.16.2 Immudb 0.9.2 Windows 10

Additional info (any other context about the problem) On Linux the code runs without any problems, this error only occurs in Windows OS

mmeloni commented 3 years ago

Thanks @rzamoramx , Im taking in charge this.

mmeloni commented 3 years ago

Hi @rzamoramx . Unable to reproduce here. I'm on windows 10 home. Launched multiple processes that are using verified* methods without problem. Could you please share your code?

rzamoramx commented 3 years ago

Hi @rzamoramx . Unable to reproduce here. I'm on windows 10 home. Launched multiple processes that are using verified* methods without problem. Could you please share your code?

Hi @mmeloni, thanks for your time, of course, I attached my code

I'm using a database and user different from the default

main.zip

Note: when I use the method Set() I don't have any problems.

I'm found this, maybe is related, but I don't know, I'm lost with this hehe

https://github.com/golang/go/issues/23468

thanks

mmeloni commented 3 years ago

Hi @rzamoramx. I worked on this theese days. We have a branch that should work. I can give you a preview if you like. Try fix/file-lock-issue M.

rzamoramx commented 3 years ago

Hi @mmeloni. Excellent, of course, I would test, but I can't find the branch

mmeloni commented 3 years ago

We have already merged it in master from 2e6d153d19415a243a887448f4dc72552d876a0a

mmeloni commented 3 years ago

Fixed with release 1.0