[Bug] Error when Adding Documents to DeepLake Dataset - LockedException about deeplake

[herrjemand]

Can confirm

[istranic]

Hi @herrjemand Thank you for raising the issue. Is there any chance that you opened the dataset in another container or machine? That's critical because the locks are machine based, and not username-based.

[herrjemand]

No. I tried opening db, got segfault from activeloop with db locked. Could not unlock it at all. Had to delete dataset

…

On Tue, 17 Oct 2023 at 4:27 AM, Ivo Stranic ***@***.***> wrote: Hi @herrjemand <https://github.com/herrjemand> Thank you for raising the issue. Is there any chance that you opened the dataset in another container or machine? That's critical because the locks are machine based, and not username-based. — Reply to this email directly, view it on GitHub <#2547 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMPOFA3HT7YJCLZLT7M65DX7VG6JAVCNFSM6AAAAAA3WWZ3MKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRUG42DANJVGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[nvoxland]

Can you send the complete error message? Knowing which lock is stuck will help diagnose the problem.

[nvoxland]

Are you able to provide any more information, @herrjemand or @mike2k11 to help troubleshoot?

[mikayelh]

hey @herrjemand,

I hope you are doing well. I am checking in to see if the issue you were experiencing is still ongoing. If not, that’s perfectly fine, but our team is always happy to assist you in fully utilizing Deep Lake. I will close this issue for now, but if the problem persists, please feel free to respond to this email or continue chatting with us.

By the way, we will be releasing the new version of our Managed Tensor Database shortly, which abstracts away issues like this. Stay tuned!

Best regards,
Mikayel