grandizzy

@0xTimepunk running with trace enabled I can see mem grows when test forks chains (there are many tests with many chains forked running at the same time so eventually OS...

yeah, I'm actively looking into this, just provided some thoughts while debugging

> @klkvr @grandizzy does this ring a bell? nothing I could think at but will do some tests shortly and try figure out if something changed to affect this. @0xTimepunk...

I am not able to locally spot any difference between June 5 forge build mentioned as working OK (https://github.com/foundry-rs/foundry/commit/fb86e5d3bf41f9cef3ccc7fbd04e1a422f20c29e) and latest (https://github.com/foundry-rs/foundry/commit/fb86e5d3bf41f9cef3ccc7fbd04e1a422f20c29e) - when running `make coverage` on https://github.com/superform-xyz/superform-core/commit/68320ffd7190db2abb9b32d5fdf4912bf04275be commit...

@Inphi yes, please open a new issue for etch, going to use this one to optimize coverage report creation. Thank you.

@0xTimepunk can we now close this issue as if I correctly remember it's not the same as original report but a forge coverage high mem usage? Pls open a new...

@0xTimepunk going to close this for now per above comment, please open a new one if still issues. Thank you!

this should be solved now with https://github.com/foundry-rs/foundry/pull/9258 please retest and reopen if still an issue. thank you!

ethers was removed and alloy is now used by default when `forge bind`. To filter out undesired bindings one could use ``` --select Create bindings only for contracts whose names...

optimistically close it per comment above, @FrankieIsLost @Autoparallel please reopen if not a solution for you. thank you