Closed mrk-andreev closed 6 months ago
Hi @mrk-andreev thanks for reaching out.
I am a bit unsure how submodule lmdb
on your environment got pinned at master
branch. On
https://github.com/man-group/ArcticDB/tree/master/cpp/third_party, it is pinned at a particular commit https://github.com/LMDB/lmdb/tree/5033a08c86fb6ef0adddabad327422a1c0c0069a, which is still available.
Thank you for your help, my bad.
Inside Dockerfile
everything is fine. I will look deeper inside my git configuration.
Describe the bug
When I try to clone repository with all submodules I face to error
Maybe https://github.com/LMDB/lmdb created a breaking change. Because when I open this project I see
mdb.master
as a major branch.I can suggest to fork all submodules into
man-group
and maintain regular updates by your side. Otherwise this case may happen again. Because some libraries are not so popular and contain a low amount of forks and stars. What do you think about that?Steps/Code to Reproduce
Execute
git clone --recurse-submodules --remote-submodules <...>
Full command:
Output:
Expected Results
No errors
OS, Python Version and ArcticDB Version
upstream (commit
0859017305d53647205abf9869c4909b0868aea0
) / OS: Linux-5.15.0-102-generic-x86_64-with-glibc2.29Backend storage used
No response
Additional Context
No response