acheron
acheron
This could be related to Node version as the previous comment suggested but it also could be a Solana setup issue. Closing because it's an old issue and there isn't...
> Is the client backwards compatible with the old IDL when resolving external relations? I haven't tried it but my intuition would say no because the old IDL is not...
> Also any plans on resolution coming to rust? Yeah, would be great to support Rust too https://github.com/coral-xyz/anchor/pull/2814.
Maybe it's because we're on `@solana/spl-token 0.3.10`? https://github.com/solana-playground/solana-playground/blob/de4d6ab2bcb3096d041e95a6a9414b5d5665bad7/client/yarn.lock#L2768-L2769
Updated to `@solana/spl-token 0.4.3` (latest) in https://github.com/solana-playground/solana-playground/commit/911a1ea2fdc09d15b2bb9db123cae8972849116f but there is a new error now which is most likely caused by the crate version this time.
People ask about this error all the time so I'm linking https://github.com/solana-labs/solana/issues/31428 once again.
The easiest way to fix this problem is to add: ```toml ahash = "=0.8.6" ``` to your dependency list in `Cargo.toml` or run: ``` cargo update -p [email protected] --precise 0.8.6...
What do you get if you run `cargo tree -i ahash`? Also, your Rust version is irrelevant because `rustc` in `cargo-build-sbf` is coming from Solana's fork (https://github.com/solana-labs/solana/issues/31428).
Looks like this got fixed in https://github.com/solana-labs/solana/pull/34636 and https://github.com/solana-labs/solana/pull/34650 so this issue can be closed.
> updated `nonblocking` client, and removed unused `Deref` import. I guess we can wait until 1.17 ships? Yes, I think it's better to wait until `1.17` adoption before we make...