Bring the comments the review left stale to the code: judge without a prompt, extract reading again, searches closing by age, the cap at 4, the affinity bonus and the cursor a sweep hands back
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
1 parent
b4774f1da9
commit
e8157d9509
7 files changed
+16
-11
No files matched your search
@@ -167,8 +167,12 @@ shared code logs, records and decides.
|
||||
handed to `rows`, its raw results as dicts with an `id` (counted, by distinct
|
||||
id, to decide completeness), the total the host states or None, and the
|
||||
cursor of the next page or None after the last. The first call gets cursor
|
||||
None. A board with a total is complete when as many distinct ids were read;
|
||||
one without, when the read ended on an empty page. A 429 after the first page
|
||||
None, and a later one may get its cursor back from JSON, a tuple as a list,
|
||||
when a sweep continues. A board with a total is complete when as many
|
||||
distinct ids were read; one without, when the read ended on an empty page.
|
||||
A reader that sees a page come again hands it over with no results and a
|
||||
cursor that is not None, which ends the read incomplete; None there would
|
||||
read as the last page. A 429 after the first page
|
||||
ends the read, incomplete; `_runner.MAX_PAGES` pages a pull at most,
|
||||
`_runner.PAGE_DELAY` apart, and a board cut there is swept across pulls
|
||||
(`_runner.read_listing`). A paged module may also have `parse(body, slug)` for one page's body.
|
||||
|
||||
+4
-4
@@ -13,10 +13,10 @@ and the saved `pages` param bounds the pages read (`DEFAULT_PAGES`, at most
|
||||
`MAX_PAGES`).
|
||||
|
||||
A search result list is never a board's complete list, so a role missing from
|
||||
one run is not closed here. A search that read everything that matches was
|
||||
complete (`complete="stated"`, as many distinct results as the stated total),
|
||||
and the pull closes what it stopped listing; the rest close once no search
|
||||
has seen them for `STALE_DAYS` (see `app/jobs/pull.py`).
|
||||
one run is not closed, also when the search read everything that matches
|
||||
(`complete="stated"`, as many distinct results as the stated total): its
|
||||
roles close once no search has seen them for `STALE_DAYS` (see
|
||||
`app/jobs/pull.py`).
|
||||
|
||||
In a pull a search is read by `_runner.read` under the prefix `search`, as a
|
||||
board is under `ats`: the 10% guard holds it, `_runner.stamp` records it,
|
||||
|
||||
Reference in new issue
Block a user