Closed glihm closed 1 month ago
Manually adding the contract with build-external-contracts
works. But is that the intended behavior for testing too?
If yes, then can be closed.
Hi!
Yes, since 2.8.3
we have stopped building all contracts from all dependencies preemptively. This is an optimization. Please take a look at the release notes https://github.com/software-mansion/scarb/releases/tag/v2.8.3
Found the release afterward, sorry didn’t close. Thank you @maciektr. 👍
Problem
Since scarb
2.8.3
, when a contract is imported from an other package, thedeploy
syscall usingother_package::contract::TEST_CLASS_HASH
panics withCLASS_HASH_NOT_FOUND
.Using scarb
2.8.2
, it works as expected.Steps
Write a second package with this test:
Which stands for
CLASS_HASH_NOT_FOUND
.Possible Solution(s)
The way crates ids are collected has changed between
2.8.2
and2.8.3
, not usingcollect_all_crate_ids
anymore.But even trying to add it back, the correct crate ids are shown, but the error seems to persist.
Notes
No response
Version