Jordan

@hfoffani on review II'm concerned with the open PRs from the maintainer. Doesn't seem like they are interested in accepting fixes at this time.

Had this same issue and ended up transitioning away from serverless for the time being.

Appreciate the pointers, we'll aware of the chain id and key config settings. Verify works fine if passed after forge script, so the etherscan api key is not the problem....

my bad @rkrasiuk this totally slipped my mind. I've in general stopped using forge-verify because I have basically had full success deploying with forge script --verify and using --resume if...

Having the same issue, also with the app store

Almost certainly a breaking change. I, like @CodeSandwich, am just using trivial unix commands to slice the output but would prefer it be opt-in given the inconsistency

+1 also have this issue

// import {EndpointV2} from "@layerzerolabs/lz-evm-protocol-v2/contracts/EndpointV2.sol"; // import {SendUln302Mock as SendUln302} from "@lz-oapp-test/mocks/SendUln302Mock.sol"; // import {SimpleMessageLibMock} from "@lz-oapp-test/mocks/SimpleMessageLibMock.sol"; The above 3 libraries all generate compiler errors when trying to run coverage.

https://github.com/foundry-rs/foundry/issues/3527 This error persists even with `--ir-minimum`

This branch needs some merge conflicts fixed && we need to rename MANAGINGDAO_XX to MANAGEMENT_DAO_XX EDIT: resolved in commit https://github.com/aragon/osx/pull/582/commits/d4dfbb9f27dd5e91e05bb6797a00cca2e21c0c2e