Problem
When Node is not available, readabilipy's pure-Python path returns no content for an empty page, and the server reports "No more content available" for start_index 0. That message is meant for paging past the end of a page, not for a simplification failure. With Node, the same page reports a simplification error.
Where it is pinned
src/fetch/tests/test_protocol.py: test_empty_html_without_node_reads_as_no_more_content, added in #4971 (Wave 1 of #4857). Each of these tests carries a KNOWN BUG marker: it asserts the current, wrong behavior, so the fix has to change it.
Expected
An empty extraction at start_index 0 reports the same simplification failure with or without Node.
Done when
- The behavior above is fixed, in the legacy-era (2025-11-25) server on SDK 1.x.
- The pinning tests assert the correct behavior, and their
KNOWN BUG markers are gone.
- The per-file 90% coverage gate still passes.
Problem
When Node is not available, readabilipy's pure-Python path returns no content for an empty page, and the server reports "No more content available" for
start_index0. That message is meant for paging past the end of a page, not for a simplification failure. With Node, the same page reports a simplification error.Where it is pinned
src/fetch/tests/test_protocol.py:test_empty_html_without_node_reads_as_no_more_content, added in #4971 (Wave 1 of #4857). Each of these tests carries aKNOWN BUGmarker: it asserts the current, wrong behavior, so the fix has to change it.Expected
An empty extraction at
start_index0 reports the same simplification failure with or without Node.Done when
KNOWN BUGmarkers are gone.