Francesco Cinà

@amarao I agree, but if you consider `on_success` as the default case, then these two are equivalent: - `recipe_1: before_1 && on_success(after_on_success_1)` - `recipe_1: before_1 && after_on_success_1` So the old...

The way I would read it: ``` myrecipe: ok1 && on_success(failed1) && on_success(failed2) && on_failure(failed3) && always(ok2) | | | | v | | v run because previous | |...

@amarao an error maybe?

I implemented a small library as a workaround for this specific issue, you can check it here: - library: https://crates.io/crates/maybe-once - how to use it with `testcontainers`: https://github.com/ufoscout/maybe-once/blob/master/examples/testcontainers/src/postgres_blocking.rs It allows...

Same issue with: ```toml revm = { version = "14.0", default-features = true, features = [ "serde", "arbitrary", "asm-keccak", "dev", "kzg-rs", ] } ```

@rakita We have investigated more and we can reproduce the error with every REVM version >= 10. Even by ignoring the `InitialCollision.json` test as shown in your code, there are...

@rakita Our tests are broken by this commit: https://github.com/bluealloy/revm/commit/9955d9faa5ca4cefc30bde3eb37ba11af7ef474d After that commit the `DatabaseCommit::commit` fn is called with a different set of changes. For example, in the case of the...

> > Should we ignore everything marked as cold? > > This is the solution. Great! Should we also ignore storage slots with `is_cold: true`?

@lmuntaner do you have an example? This still shows the old UI: ``` dfx deploy internet_identity --argument " (opt record { new_flow_origins = opt vec { \"https://id.ai\" }; })" ```

Still not working: ``` sha256sum ./target/artifacts/internet_identity.wasm.gz 30d9ccec1ac75431943331d69b5cce3f585b1c0f09e2a7fac771182e0fab3440 ./target/artifacts/internet_identity.wasm.gz ``` ``` dfx deploy internet_identity --argument " (opt record { new_flow_origins = opt vec { \"http://rdmx6-jaaaa-aaaaa-aaadq-cai.raw.localhost:8000\" }; })" ```