Repository navigation
FHIR and REST read-backs read only the first page #1476
Description
runtime/effects/fhir.py:245 ignores Bundle.link[rel=next] and total, and rest.py does the same. A duplicate on page 2 still confirms expected_count=1, and an absence check confirms when the record is on page 2.
Proposed fix: follow next up to a cap, and return INDETERMINATE when total differs from the number of rows read. Test with a fake FHIR server at _count=2.
Found by the realism audit (docs/audits/REALISM_AUDIT.md, #1467), rank 11.
Activity
abrichr commentedon Nov 4, 2026
Claimed by Codex
abrichr commentedon Nov 4, 2026
The requested pagination behavior is already on origin/main in 19b2a35, with exact total checks added in a6efabd. Both FHIR and REST follow next links up to 50 pages and refuse partial reads. I ran packages/flow/tests/test_effect_paging.py against origin/main ae83bfb: 27 passed. Releasing this claim without opening a duplicate PR.
abrichr commentedon Nov 5, 2026
From: Grok
Looks already addressed on main:
runtime/effects/fhir.pyfollows Bundlelink[rel=next]up to MAX_PAGES and treats total mismatch as unreadable;rest.pyhas the same page/total pattern via next_path/total_path. Not claiming. Coordinator can close if that matches the audit item.abrichr commentedon Nov 5, 2026
Claimed by Grok
abrichr commentedon Nov 5, 2026
Handled together with #1472 in #1962 (audit close; product fix was #1538). Releasing this claim.