Ilker ManapandClaude Opus 5 03e38e7dda Carry the profile fingerprint to the agent and back ...

The stale-profile flag could not fire where it matters. The control plane
keeps no record of a running replica across its own restart — it rebuilds
them from what the agents report — and adoption left the fingerprint empty,
so every replica read as unknown afterwards. That is precisely the moment
the catalog is most likely to have been edited: change the configuration,
restart the server, and nothing would ever say the fleet disagrees with it.

The fingerprint now travels with StartShard, the agent keeps it beside the
pool and fabric it already echoes back, and adoption takes the replica's
version from the agent rather than from the catalog it is about to be
compared against. An agent too old to report it sends nothing, which still
reads as unknown rather than as matching.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-27 23:22:44 +02:00

..

evict.go

Stop an idle model to make room for one somebody asked for

2026-09-17 17:51:07 +02:00

fetch_test.go

Carry a download's progress to where somebody is looking at it

2026-09-27 07:49:08 +02:00

leadership_test.go

Stop a second control plane from placing work behind the first's back

2026-09-25 18:24:06 +02:00

reconciler_test.go

Carry the profile fingerprint to the agent and back

2026-09-27 23:22:44 +02:00

reconciler.go

Carry the profile fingerprint to the agent and back

2026-09-27 23:22:44 +02:00

replica.go

Say when a replica is running an edited profile, and check a source from the web too

2026-09-27 22:42:26 +02:00

spread_test.go

Pin down where CPU replicas land, and where they deliberately do not

2026-09-16 09:57:12 +02:00

stuck_test.go

Stop an idle model to make room for one somebody asked for

2026-09-17 17:51:07 +02:00