-
Notifications
You must be signed in to change notification settings - Fork 5
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
Build error due to penumbra-proof-params
use of Git LFS
#29
Comments
We plan to use a submodule dependency for now, to keep our build infra on the rails. However, a submodule isn't ideal into the future. Part of why we maintain Galileo is that it gives us a perspective on what it's like to build external tools against Penumbra. Now that we're adding zk proofs, we don't want to require third-party developers to submodule-in the dependency. More investigation required for a long-term solution. |
We recently started using git-lfs in the penumbra repo, and cargo can't fetch lfs artifacts via a git dependency. For now, we'll clone the penumbra repo side-by-side and build from relative path. Refs #29.
We recently started using git-lfs in the penumbra repo, and cargo can't fetch lfs artifacts via a git dependency. For now, we'll clone the penumbra repo side-by-side and build from relative path. Refs #29.
We recently started using git-lfs in the penumbra repo, and cargo can't fetch lfs artifacts via a git dependency. For now, we'll clone the penumbra repo side-by-side and build from relative path. Refs #29.
We went with a relpath for now, and are able to build successfully again. We'll need to revisit this, but we have a workaround for now. |
Galileo fails to build due to being unable to resolve Git LFS pointers is the dependency
penumbra-proof-params
. This can be seen in this CI job.@plaidfinch found this issue indicating that Git LFS assets in dependencies is not supported by cargo: rust-lang/cargo#9692
During release of Lysithea (penumbra-zone/penumbra#2005) we temporarily used a path dependency to get galileo to build.
Another option suggested by @plaidfinch is to use a submodule, which @conorsch volunteered to take a look at.
The text was updated successfully, but these errors were encountered: