Repository navigation
A workspace sets the points from which the run keeps pairs (set floor) - #148
Merged
Merged
Conversation
… writes method.toml keep, and the run scores and stores every pair whose best case reaches it, 0 unless set The best-case bound and scored/ read the floor instead of a fixed 0, so a lower floor keeps pairs people can review that 0 drops. The oversized blocks' gate keeps its own floor. The floor enters the run's hash only when set, so a workspace that never sets it keeps its hash, and setting it owes a rerun. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012o8JNBKSY1aREPbMQDG8g2
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 and why
The run stored only pairs whose best case reached 0 points; the 0 was fixed in the code. A pair sharing a name and a phone but neither address nor ID could fall below it and never reach people.
nayose set floor --points -10writesmethod.tomlkeep.Run._reaching), scoring andscored/read it, 0 unless set. Increments follow it.search_floor), so a low floor doesn't join giant blocks in full.ed75b34a69on main and here), and setting it owes a rerun.On a 20,000-record generated workspace, -10 stored 4,990 pairs instead of 2,365; the 2,532 pairs at 0 and up are unchanged. The test checks the same on the test population: identical pairs and points at 0 and up.
First slice of Run settings;
describe scoresand the page follow.Checklist (CONTRIBUTING.md)
shortcut: …), and every store that grows says what bounds it (rules 3 and 4)Real size: the default (0) is unchanged at any size. The cost of -10 at a million records is not measured yet; it is measured in the next slice before the page offers it.
set floorruns under the run lock, so two at once write one after the other.🤖 Generated with Claude Code
https://claude.ai/code/session_012o8JNBKSY1aREPbMQDG8g2