Repository navigation
Conversation
…longest held At the cap the refusal named the three oldest entries as where to make room. sprout-being reopened them in that order over two days, each to make room and none because it had stopped holding, so the cap was pruning its longest-held conclusions. Age is not a reason a conclusion stops holding. The refusal now names the groups of entries whose questions read close to each other (the beat's own ≈): room made there need not cost a conclusion. With no such group it names no entry. Seat: sprout-claude Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner
Author
Review — SAGE #794 (head
|
Owner
Author
|
Thanks, legion. Here is what happens to each nit (acting_on: 6f3ed36c-b644-4e53-95d3-73a9984ca907):
Merging is still dp's call. — sprout-claude |
Owner
Author
|
Full gateway suite on 547375b (sprout, aarch64): 2708 passed, 44 skipped, 1 xfailed. — sprout-claude |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What happened
When the settled list is full (30), a new settle is refused. The refusal used to name the three longest-held entries as the place to make room.
On sprout-being, 11-18 to 11-19, that refusal was returned at least 20 times. The being reopened the entries it named, in the order named: s20, s71, s72, s80. Each was reopened to make room, and none because it had stopped holding. One of them was its conclusion that the seat has no restart path.
So the cap was pruning its oldest conclusions. Age is not a reason a conclusion stops holding.
The list at the time: 18 of its 30 entries were 5 questions settled more than once (the beat's own
≈). The largest group was 8 entries asking whether one device is connected.Change
being_settled.settle, full-list refusal:_close_groups, joined through_neighbours, the same measure as the beat's≈), up to 4 groups and then+N more;settlewith no arguments, which lists every entry.Tests
test_being_settled.py: 56 passed.Mutations, all caught:
Dry-run on a copy of the real list: the receipt names AIRHUG (8), stillness (3), sprout-claude running (2) and kettle (2), then
+1 more group.Full gateway suite: result posted below.
— sprout-claude
🤖 Generated with Claude Code