# fix\(server\): hub usage pacing keeps forget atomic and drops stale entries · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/1006a51c193ddf6e1b2f0c93e363c812132a107e)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: 1006a51c193ddf6e1b2f0c93e363c812132a107e

Requested commit: 1006a51c193ddf6e1b2f0c93e363c812132a107e

Commit: 1006a51c193ddf6e1b2f0c93e363c812132a107e

Tree: 21a5a0d840c0be7b9fbb5fc9d80eed0db747e9f7

Author: Yannic Charlon

Committer: Yannic Charlon

## Message

```
fix(server): hub usage pacing keeps forget atomic and drops stale entries

The forget check and the store now happen in one Ref update, guarded by a
single forget counter, so a forget can't land between them and an older
answer can't come back. A failed request rechecks the last answer's age once
it settles, and entries too old to pace or stand in are pruned on each store.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

```

## Parents

- [3e78ed73a1414175b205f0f1167b7a8cc52c22e9](https://git.cafe/pingdotgg/t3code/commit/3e78ed73a1414175b205f0f1167b7a8cc52c22e9?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/1006a51c193ddf6e1b2f0c93e363c812132a107e?format=markdown)