docs(docs): R5.4 emoji refusal named at the guard, round 12 residuals declared
This commit is contained in:
1 parent
c4e717da86
commit
88e42749ec
4 files changed
+152
-6
No files matched your search
@@ -3136,7 +3136,9 @@ Parity, every expectation written by the TypeScript (`tests/curation_review.rs`,
|
||||
moved, an added and a polygon marker, a path marker on a detail view framed by its view box,
|
||||
a sheet with nothing but a level A change: raw and aligned Markdown byte for byte, the
|
||||
overlays byte for byte, the application's drawings byte for byte or under the declared rule;
|
||||
an emoji in a cell gives the same raw text and the declared refusal at the alignment (R5.2);
|
||||
an emoji in a cell gives the same raw text and a declared refusal: the report guard refuses it
|
||||
first (`UnsupportedMarkdown`, a character outside the allowlist), before the aligner's
|
||||
`UnsupportedWidth` (R5.2) is reached;
|
||||
- two runs byte-equal; an undeclared difference (a colour, a coordinate) refused with and
|
||||
without the rule.
|
||||
|
||||
@@ -3202,7 +3204,7 @@ pass the guard unchanged.
|
||||
| Input | TypeScript | Rust |
|
||||
|---|---|---|
|
||||
| authored text outside the allowlist: Markdown Prettier rewrites (`*x*`, `_x`, `x_**a**`, `**a****b**`, `Voir_https://…`, `a b`, a non-ASCII space, a tab, a line break in a list item, `` `` ``, `a\|b`, `[a](<b>)`, `[[ a ]]`, `*`…), the constructs refused whole (links, HTML tags, autolinks, character references) and any character outside the admitted set (pictographs, symbols, combining marks without the Alphabetic property; an alphabetic mark such as U+0345 is a letter and Prettier aligns it alike) | written, then rewritten by Prettier (escapes, `_emphasis_`, collapsed spaces, indented continuation lines, normalised links; a row with an extra cell), or kept | refused (`UnsupportedMarkdown`), even where Prettier would have kept the text |
|
||||
| a pictograph in a table cell (an emoji, and ©, ®, ™, ✓, ★, ⚠ and the other characters `text::is_emoji_candidate` lists) | measured with Prettier's tables | refused (`UnsupportedWidth`, R5.2): the set is wider than the emoji, the refusal stays loud |
|
||||
| a pictograph in a table cell (an emoji, and ©, ®, ™, ✓, ★, ⚠ and the other characters `text::is_emoji_candidate` lists) | measured with Prettier's tables | refused, loudly: in the draft's two reports by the guard first (`UnsupportedMarkdown`, outside the allowlist), the aligner's `UnsupportedWidth` (R5.2) applying there only to the alphanumeric candidates (Ⓜ, 🅰) and in IMPORT-REPORT; the set is wider than the emoji |
|
||||
| aligned report tables past 32 Mi display columns in all (rows × padded row width, the CHANGELOG's three level tables summed; the equine CHANGELOG's widest table is about 0.5 MB): one long authored cell pads every row of its level, so an 80 KB rationale over 14,000 records asked for 1 GB (security gate R5.4 round 6) | Prettier aligned it (the same amplification) | refused (`Guard`): the CHANGELOG's tables are projected from their cells (bytes bound the display width) before the raw table is joined (test `a_changelog_whose_alignment_would_explode_is_refused_before_it_is_built`, through the pipeline), every other table in the aligner before any padded row is built (test `an_aligned_table_past_the_bound_is_refused_before_it_is_built`), import report included |
|
||||
| records weighing more than 16 Mi units in all (`records::record_weight`, about the bytes in memory: 64 per JSON value and per string, plus one per byte of text, for the values, the change and the op, which each record clones; the equine records weigh 1,966,163; an add or a move also clones its position anchor): a rename or a remove records the whole item and one op, or the B/C marking, records once per item it reaches, so 400 renames of a 5,000-child item asked for 4.3 GB (round 7), a level B add of 10,000 children with a 128 KiB rationale 1.37 GB inside one marking, a 64 KiB value set over a subtree 2.0 GB (round 8), 200,000 one-character reference ids cloned into each record 948 MB at one unit per byte (round 9) | recorded (the same copies) | refused at the record that passes the bound, charged before the change and the op are cloned into it (`records::charge`, tests `the_records_cannot_outgrow_their_bound`, `the_records_bound_holds_inside_one_op_and_the_marking`); the raw report rows, built from the records, are bounded with them; the 200,000-value document bound now holds the baseline (test from a padded baseline) |
|
||||
| review drawings past 64 MiB in all, projected as an upper bound before any is rendered (`pipeline::review_drawings_bytes`: per view, the cleaned drawing twice with 4,096 bytes each for the drawing's fixed parts (layer group, overlay group and legend), plus for each annotation of the view in the overlay's two documents and in the application's drawing 1,024 bytes and 24 times its JSON text and the longest view name, four copies escaped up to six times longer; the equine draft projects 1,406,812 bytes for 564,239 written): 2,000 views asked for 547 MB (security gate R5.4 round 8), unnamed triggers repeating a long opened view's names 131 MB from a 485 KB changeset (round 10) | written | refused before rendering (`pipeline::MAX_REVIEW_DRAWINGS_BYTES`, tests `review_drawings_past_their_bound_are_refused_before_rendering`, `unnamed_triggers_repeating_a_long_view_name_are_refused_before_rendering`; the projection bounds what is written, a draft without annotations included: test `the_drawings_projection_bounds_what_is_written`) |
|
||||
@@ -3248,7 +3250,13 @@ value into each item before recording it, so the document holds at most as many
|
||||
records bound admits; the comparison of `--check` looks up each trigger's view linearly (views ×
|
||||
triggers, the views bounded through the drawings bound); parsing `changes.json` (R5.3 code) holds
|
||||
about 65 times the file in memory (about 1 GB at the 16 MiB read cap, security gate R5.4 round 9),
|
||||
before any bound of the applier applies; and the allowlist admits the invisible Hangul fillers (U+3164, U+115F, U+1160,
|
||||
before any bound of the applier applies, and `references.json` goes through the same parser (the
|
||||
same order, not measured); two scans are quadratic but out of reach or bounded (security gate
|
||||
R5.4 round 12): `report_guard::underscore_pairs_later` on a line of many code spans and plain
|
||||
underscores (53.7 s on a synthetic 900 KB line; the generator writes at most two plain parts
|
||||
that can carry an authored `_` per line, so it stays linear), and `pipeline::review_drawings_bytes`
|
||||
walking views × annotations before its bound applies (about 2 s at the 200,000-value document
|
||||
bound); and the allowlist admits the invisible Hangul fillers (U+3164, U+115F, U+1160,
|
||||
U+FFA0, letters Prettier keeps, no structure); the residual risks of §11.13 stand.
|
||||
|
||||
Conditions for R5.5: the owner's validation of this checkpoint; the upload tool (`ureq`, the
|
||||
|
||||
Reference in new issue
Block a user