-
Notifications
You must be signed in to change notification settings - Fork 7
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
cache doesn't work snforge_scarb_plugin
#37
Comments
Hey! I recommend upgrading your project to the latest Scarb and Foundry and enabling this: https://foundry-rs.github.io/starknet-foundry/appendix/scarb-toml.html?highlight=prebuil#toolscarb. This will Rust compilation altogether for you. Is doing this upgrade OK for your project? |
We are using But I noticed, starkli released a new version yesterday, making We are currently deploying the contracts on PS. I may be unaware of Starknet ecosystem versioning convention 😅 |
Ah, contracts compiled with scarb/cairo >=2.10 can be deployed on starknet 0.13.4 which is gonna happen very soon on mainnet, but is not there yet: https://www.starknet.io/developers/roadmap/ Try clearing caches for your actions here: https://github.com/informalsystems/ibc-starknet/actions/caches. We took a look at your runs, and it looks like our action had some stale cache that it didn't want to invalidate. This action uses |
Thanks for the roadmap link ! Looks good enough for us. We will upgrade the versions soon. About the cache, you're totally right 😅 I can't find This is the key of the cache: Since, we don't have any |
Problem
We have a dev-dependency to
snforge_std
which pullssnforge_scarb_plugin
. It seems, the caching doesn't work for it as it is a proc_macro plugin and always starts recompiling using cargo.(note: this is a dev-dependency and
snforge_scarb_plugin
shouldn't even be pulled whenscarb build
is called. but that's a separate issue forscarb
)Note that the cache works fine for other dependencies. It is only
snforge_scarb_plugin
for which the cache doesn't work.Steps
No response
Possible Solution(s)
No response
Notes
No response
The text was updated successfully, but these errors were encountered: