GameCult/Epiphany
Archived
Watch
9
0
Fork
You've already forked Epiphany
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Rule out a hidden dependency on the leaf

Browse source 
The workspace's inverse dependency tree lists the leaf alone in every
dependency kind, so the recompile of epiphany-core after a leaf-only
change was a shared target directory evicting a fingerprint under another
session's build, the accepted cost of sharing one directory. Not a
dependency, and not the explanation Hands gave.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
Meta Vens 2026-09-16 17:28:03 +02:00
commit 3bd0826d48
1 changed files with 9 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

12
notes/eureka-pipeline-state-cut.md
View file

@ -1964,9 +1964,15 @@ moves to this commit.
(Cut 6 proved no path in either direction, and Soul's pass on the
Epiphany half saw it finish in half a second untouched). Either a
shared target-dir fingerprint was evicted by another session's build,
or something depends on the leaf that this map says does not. The next
Soul in this tree checks `cargo tree -i epiphany-pipeline` and the
fingerprint reason with `CARGO_LOG=cargo::core::compiler::fingerprint=info`.
or something depends on the leaf that this map says does not. **Self
checked the second half at once**: `cargo tree --workspace -i
epiphany-pipeline -e normal,build,dev` lists the leaf alone, so no
workspace crate depends on it in any kind. What remains is the shared
target dir: another session was building Ghostlight into it during this
pass, and a fingerprint evicted by a different environment or profile
reads as a "recompile" of an untouched crate. That is the build-economy
cost of one shared `CARGO_TARGET_DIR` across sessions, already accepted
(correction 22); not a dependency, and not Hands' explanation either.
## Cut 7. Retire Huginn's TypeScript body