freeeve / roaringrange / 27305601260
65%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 7
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 85.137%. Remained the same
27305601260

push

github

freeeve 
fix(search-lambda,openalex): incremental server paging; auto-route disabled

The 'roaring bitmaps' report unwound to three layered problems:

- The deployed Lambda predated the v3 cutover AND its env still named
  the retired 47M artifacts - a different doc-ID space - so every
  server-mode response since the 484M migration rendered unrelated
  records, silently. Redeployed from current code against
  openalex-full.{rrs,rrf} (the seminal paper now returns at #2,
  matching the local ground truth).

- The handler's page-0 exact total ran the FULL tail intersection,
  which the 484M corpus pushes past API Gateway's hard 30-second cap
  on common-trigram queries. It now mirrors the client cursor: ids
  page the tail incrementally (bounded work at any offset), total is
  loaded-so-far with a 'more' flag (rendered as N+), and page 0 adds
  the KB-scale header-derived count ({count, exact}) from task 026.
  goPageServer consumes the new contract through the existing
  tailPending/countBound display machinery.

- Auto-routing is disabled by choice (AUTO_ROUTE = false): the heavy
  queries it routed are the ones the server answers slowest, so
  server-side stays an explicit toggle. The cost machinery remains.

The demo now calls the Lambda same-origin through a new CloudFront
/search behavior (origin: the regional API Gateway). New get_records
example: id-targeted record dumps for grounding ranked results.

653 of 767 relevant lines covered (85.14%)

11.68 hits per line

Jobs
ID Job ID Ran Files Coverage
1 27305601260.1 7
85.14
 GitHub Action Run
Source Files on build 27305601260