Replies: 4 comments 9 replies
-
Beta Was this translation helpful? Give feedback.
0 replies
-
|
@DOsinga could you please help with this issue? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
hi - sorry for the slow reply. I'm guessing we use v8 for the code mode that we have. @alexhancock could we make this an optional dependency and not have code mode if not found? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
@jh-block an intresting error while since 1.26 + /usr/bin/cargo auditable build -j4 --offline --locked --release --package goose-cli --features disable-update
[ 37s] error: failed to get `ahash` as a dependency of package `goose v1.26.0 (/home/abuild/rpmbuild/BUILD/goose-1.26.0-build/goose-1.26.0/crates/goose)`
[ 37s]
[ 37s] Caused by:
[ 37s] failed to load source for dependency `ahash`despite |
Beta Was this translation helpful? Give feedback.
7 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello team! I'm maintaining goose CLI in openSUSE & i have observed that the latest version has introduced the v8 crate as dependency to the project. Since OBS does not allow downloading binaries from internet during build time, it's throwing an err
[ 203s] error: failed to run custom build command for v8 v145.0.0Does the
goose-clicrate really need the v8 engine as build / runtime dependency? Your help is greatly appreciatedBeta Was this translation helpful? Give feedback.
All reactions