Mathieu

thank you very much 🙏

looks good now !

hm actually I think there is a very specific issue that happens in specific test cases that end up running forever: CI took 6hrs to run and ended up failing...

I just hit an issue when running locally: ``` * thread #6, name = 'stStaticCall::test_static_ABAcalls0_d1g0v0_Cancun', stop reason = EXC_BAD_ACCESS (code=2, address=0x170633e80) frame #0: 0x000000017280212c 504898746202199744673968940527932241844513528453156538068464172101734859290`impl$evm::instructions::memory_operations::MemoryOperation::exec_pc(f179) + 18816 504898746202199744673968940527932241844513528453156538068464172101734859290`impl$evm::instructions::memory_operations::MemoryOperation::exec_pc(f179): -> 0x17280212c...

^ so actually the above happens if after I increase the default stack size with `export RUST_MIN_STACK=16777216`. If I don't, it just stack-overflows. Same repro instructions as in this issue...

@tcoratger can you help here?

@azteca1998 i'm unable to repro your issue from a fresh clone. I have: ``` ❯ rustc --version rustc 1.81.0 (eeb90cda1 2024-09-04) ``` can you try a `cargo clean` and to...

it's done in https://github.com/foundry-rs/starknet-foundry/pull/2396 already

The easiest way would be to use python to generate cairo code, like so: ``` def generate_powers_of_two(): print("pub const POW_2_256: [") print(" u256") print(" ; 256] = [") for i...

hi @augustin-v it seems that the changes brought in scope of these PR highlight a memory-management related issue in Cairo Native which crashes our CI runner, thus I will have...