The task worker (archie-agent) runs presence.Run for itself. Every 30 seconds it makes a State Store write (upsert plus a prune of all stale presence rows) over its task grant. When that call fails, the worker logs WARN "presence not reported" through the task's system-log handler, so it appears in the task's Log tab: repeated every 30-60 seconds with run credentials unavailable or context deadline exceeded. Nothing reads the per-task agent presence rows: the service list in presence.Services() excludes the agent, and the dashboard only uses the name to filter logs. The table kept 30 agent rows in a day, each retained 24 hours.
Done when
The worker no longer reports presence, and the grant's allowance for PutPresence is removed with it.
A parked task's Log tab shows no presence lines.
Verified by a test that the task grant rejects PutPresence.
## What is wrong
The task worker (`archie-agent`) runs `presence.Run` for itself. Every 30 seconds it makes a State Store write (upsert plus a prune of all stale presence rows) over its task grant. When that call fails, the worker logs WARN "presence not reported" through the task's system-log handler, so it appears in the task's Log tab: repeated every 30-60 seconds with `run credentials unavailable` or `context deadline exceeded`. Nothing reads the per-task agent presence rows: the service list in `presence.Services()` excludes the agent, and the dashboard only uses the name to filter logs. The table kept 30 agent rows in a day, each retained 24 hours.
## Done when
- The worker no longer reports presence, and the grant's allowance for `PutPresence` is removed with it.
- A parked task's Log tab shows no presence lines.
- Verified by a test that the task grant rejects `PutPresence`.
Fixed in 260e9fc4: worker presence reporting, its transport method and the task-grant allowance for PutPresence are removed; a test asserts the grant rejects PutPresence.
Fixed in 260e9fc4: worker presence reporting, its transport method and the task-grant allowance for PutPresence are removed; a test asserts the grant rejects PutPresence.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What is wrong
The task worker (
archie-agent) runspresence.Runfor itself. Every 30 seconds it makes a State Store write (upsert plus a prune of all stale presence rows) over its task grant. When that call fails, the worker logs WARN "presence not reported" through the task's system-log handler, so it appears in the task's Log tab: repeated every 30-60 seconds withrun credentials unavailableorcontext deadline exceeded. Nothing reads the per-task agent presence rows: the service list inpresence.Services()excludes the agent, and the dashboard only uses the name to filter logs. The table kept 30 agent rows in a day, each retained 24 hours.Done when
PutPresenceis removed with it.PutPresence.Fixed in
260e9fc4: worker presence reporting, its transport method and the task-grant allowance for PutPresence are removed; a test asserts the grant rejects PutPresence.