acheron

> Weirdly enough, the main issue is opening the actual file. Especially when this file is shipped in an npm package. Once read, parsing the json payload is easy. >...

Yeah I agree, this would be super useful. One way to achieve this would be to fetch the Anchor IDL on-chain(https://github.com/solana-playground/solana-playground/issues/93) if it exists.

> For auction-house example, did you reproduce the issue with the client https://github.com/armaniferrante/auction-house/blob/armani/pda/tests/auction-house.ts ? I wonder if I can get it just using this repo as starting point Yes. Switching...

@KirillLykov you can see [this run](https://github.com/coral-xyz/anchor/actions/runs/5163063292/jobs/9301226421). It shows exactly what commands to run to reproduce it. From the same CI logs: ``` 1) auction-house Creates an NFT mint: Error: failed...

@KirillLykov here is a script to reproduce the issue: ```sh #!/usr/bin/env bash set -e # Set solana version solana-install init 1.16.0 # Create a temp directory mkdir data-too-large-error pushd data-too-large-error...

@KirillLykov thanks but I'll note that those versions hasn't changed in ~2 years and they were also tested with every Solana release within the last ~2 years(without having to change...

> > After downgrading to `1.14.20`, the version of cargo used in `cargo-build-sbf` is `1.62-dev`. And a lot indirect dependencies (i.e. spl-token) need cargo version to be greater than `1.64`,...

> I was confused with the original message, I thought it is about solana and borsh update which lead to the current problem. Now it looks to me that this...

> @acheroncrypto could you confirm that this summary is correct? Yes, it's a good summary overall but I'm not fully convinced of the analysis for the following reasons. > *...

Looking to publish a new release soon, and it would be great to get this in too. Could you check out https://github.com/solana-playground/solana-playground/pull/206#discussion_r1510001684?