bug(`forge build`): `failed to read artifact source` error when previously built source file is removed

[frolic]

Component

Forge

Have you ensured that all of these are up to date?

• Foundry
• Foundryup

What version of Foundry are you on?

forge 0.2.0 (e215f3f 2024-10-08T00:25:05.208317000Z)

What command(s) is the bug in?

forge script, forge build

Operating System

macOS (Apple Silicon)

Describe the bug

I don't recall this happening before and seems to have surfaced recently. This generally happens when you are working on a .sol file, forge build, then remove the source file before building again. Forge seems to still want to find the source file by its artifact. I see this most often when switching branches where Solidity files come and go.

To fix/workaround, I have to forge clean manually, but would expect forge to be smart enough to figure this out.

running "forge script PostDeploy --broadcast --sig run(address) 0x8D8b6b8414E1e3DcfD4168561b9be6bD3bF6eC4B --rpc-url http://127.0.0.1:8545 -vvv "
[⠊] Compiling...
No files changed, compilation skipped
2024-10-08T17:37:00.688771Z ERROR foundry_compilers_artifacts_solc::sources: error="/Users/kevin/Projects/paymaster/packages/contracts/node_modules/@account-abstraction/contracts/interfaces/UserOperation.sol": No such file or directory (os error 2)
Error: Error: 
failed to read artifact source file for `/Users/kevin/Projects/paymaster/packages/contracts/node_modules/@account-abstraction/contracts/interfaces/UserOperation.sol`

Context:
- "/Users/kevin/Projects/paymaster/packages/contracts/node_modules/@account-abstraction/contracts/interfaces/UserOperation.sol": No such file or directory (os error 2)
Error running "forge script PostDeploy --broadcast --sig run(address) 0x8D8b6b8414E1e3DcfD4168561b9be6bD3bF6eC4B --rpc-url http://127.0.0.1:8545 -vvv "

[zerosnacks]

Related: #6572

Not marking as a duplicate as your description is more general, updated the title for better searchability.

For the time being, as you mentioned it is currently recommended to run forge clean if you run into this.

[frolic]

Is this an easy thing to fix within foundry? Our team and users run into this fairly regularly and it's especially jarring for new users. We're tempted to catch this specific error and run forge clean automatically but wanted to know if this is an easy thing to fix internally first.

For context, we do a lot of Solidity codegen and this shows up often when switching between branches where Solidity source files (often codegen) are changing.

[zerosnacks]

Hi @frolic, thanks for drawing attention to this

Would it be possible to create a minimal reproduction for this? It would greatly help us narrow down the root cause.
It could also be instructions on the latticexyz/mud repo this reproduce this, ideally consistently.

I remember running into it at some points in the past but it is always in an odd state that is difficult to replicate and in many cases not reproducible reliably.