User Tools

Site Tools


provenance:design:blocking_and_geodifference

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
provenance:design:blocking_and_geodifference [2026/09/10 23:49] – Fix two rendering defects found by checking the rendered DOM: a literal <div id="root"> inside ''monospace'' truncated the page from section 11 onward (inline code does not escape tags), and every internal link was namespace-relative from provenance:. Aut karel.kubicek.claudeprovenance:design:blocking_and_geodifference [2026/09/10 23:50] (current) – The sentence describing the namespace-relative-link bug contained a live example of it and rendered a red link; escape it with %% and say so. Authored by Claude. karel.kubicek.claude
Line 380: Line 380:
   - **Two "quotes" came from the extraction's model-written ''summary'' field** and were replaced with the papers' own words (§9). Nothing was published in that state, but the checker had to be extended to catch the class rather than the instance.   - **Two "quotes" came from the extraction's model-written ''summary'' field** and were replaced with the papers' own words (§9). Nothing was published in that state, but the checker had to be extended to catch the class rather than the instance.
   - **''scripts/sitemap.mjs'' reported a failure that was not one.** It caches page source under ''out/pages/'' and never expires it, so a roadmap row removed twenty minutes earlier still showed as "WRITTEN but still on the roadmap". The cache entry was refreshed by hand; the script's cache policy is a known trap rather than a bug found here.   - **''scripts/sitemap.mjs'' reported a failure that was not one.** It caches page source under ''out/pages/'' and never expires it, so a roadmap row removed twenty minutes earlier still showed as "WRITTEN but still on the roadmap". The cache entry was refreshed by hand; the script's cache policy is a known trap rather than a bug found here.
 +  - **A literal ''%%<div id="root">%%'' inside monospace truncated this page from section 11 onward**, and it was live in that state for about two minutes. DokuWiki's inline code does **not** escape a tag: everything after it was dropped, silently, with no error and no failing check — ''check_wrap.mjs'' and ''check_tables.mjs'' both passed on the source. It was caught by fetching the **rendered DOM** and comparing its heading, table and ''<file>'' counts against the source's. Nothing but reading the render catches this class.
 +  - **Every internal link on this page was namespace-relative.** From ''provenance:design:'', ''%%[[roadmap]]%%'' resolves to ''provenance:design:roadmap''. Every link here is now root-anchored with a leading colon, and the rendered DOM was checked for ''wikilink2'' (red-link) classes. **Writing that sentence produced a third instance of the same bug**: the example link, in monospace, was still a live link and rendered red, because inline code does not escape a wiki link any more than it escapes a tag. It needs ''%%…%%'' — which is what the sentence you are reading now uses.
   - **''report_blocking_geodifference.mjs'' exhausted the V8 heap on its first run**, because it cached every paper's full text (0.5 GB on disk, over 4 GB as JS strings). It now does a single streaming pass for the whole-corpus regexes and caches only the 63 population texts.   - **''report_blocking_geodifference.mjs'' exhausted the V8 heap on its first run**, because it cached every paper's full text (0.5 GB on disk, over 4 GB as JS strings). It now does a single streaming pass for the whole-corpus regexes and caches only the 63 population texts.
  
provenance/design/blocking_and_geodifference.1789084158.txt.gz · Last modified: by karel.kubicek.claude