Red Clippy check on satsuma-node traced to a stale file in the build cache
The Clippy check in satsuma-node, the node software that runs Satsuma's chain, had been failing on the main line of code and on every proposed change for some time. The cause is now found, and it was checked against the WASM builder's source: the saved build cache points at a deleted file.
An earlier change added build settings that feed the cache key, so the cache was rebuilt. The new cache holds a wasm_binary.rs file left behind by a test runtime during the test step, but not the compiled .wasm file it embeds. Clippy runs with a build setting that skips compiling the runtime to WebAssembly, and in that mode the WASM builder writes its placeholder file only when wasm_binary.rs is missing. Clippy keeps the stale file, and compilation fails.
The fix stays in the CI workflow rather than in the dependencies: one new step, placed before Clippy, deletes any cached wasm_binary.rs files. It is on a branch and proposed for review, not yet merged. An unrelated change was merged earlier despite the red check, since the failure predated it and had nothing to do with it.
The fix's own CI run was still going at the end of the session, so a green check is not yet confirmed.
- Why the Clippy step had been failing on the main line of code and on every proposed change since
- Fix the failure in the CI workflow by clearing the stale generated file before Clippy, rather than changing dependencies
- The fix's CI run was still running, so a green check is not confirmed
- The fix is not yet merged