onbjerg

See my comment here on ideas I had for `forge doc`: https://github.com/foundry-rs/foundry/issues/1410#issuecomment-1109824780 Also see the original issue: https://github.com/foundry-rs/foundry/issues/1410#issue-1214179443 I've closed that issue to roll it up into this one

Issues with missing receipts are separate from this one and *should* be fixed, but if not, please open an issue for this - closing this one as per Joshie's comment

You might have caught it just before the contract was verified. It goes through some stages: pending (what you got here), failed or successful. You can make it retry with...

Closing as duplicate of #2673 since the underlying code will be the same

So the idea is to move away from submodules, but still depend on git for fetching/updating (at least for now)? In terms of ~/.foundry/registry we could symlink to the package...

Would this not work with symlinks? Otherwise I think it would be ok to just copy and have `~/.foundry/registry` act as a cache

Another idea as well: since we would have better insight into dependencies/packages, for packages that support it we can generate more "sane" automatic remappings. For example, could provide a way...

For now we'll try to improve the error messages, but we should also explore if we can avoid panicking by extending REVM's `Database` trait

This should now be handled more gracefully

i think this is ok, simple enough to resolve #2451, not so big that it will cause a lot of churn over what to add/remove etc no need to add...