XAML package: large resource dictionaries are cut off and reported as extract.unsupported_syntax #312

Closed
opened 2026-10-04 20:17:58 +02:00 by buildagent · 1 comment
Member

Field report from the TimeLine project (de.h-dv.xaml, via resolution_gaps), 2026-10-04.

Four XAML files are only partly indexed:

  • Themes/Icons.xaml (the client's shared icon resources): extract.unsupported_syntax
  • DevExpress.Xpf.Charts/Generic/Pie2DModels.xaml: extract.unsupported_syntax
  • two code-generator templates / expected outputs: extract.parse_error. These are expected: the files contain template placeholders.

Impact: uses of an icon key that appear after the point where extraction stopped are missing from the index. "Where is icon X defined or used" undercounts, and the agent has to fall back to search_text.

Likely cause: _prdoc/records/80-S12-xaml-reference-package.md §5 describes two ceilings that emit extract.unsupported_syntax:

  • a 4,096-byte NAME ceiling on an attribute value;
  • a 196,608-byte response-BODY ceiling.

Icon and 3D-model dictionaries hold very long geometry strings (Data="M…", Geometry, Points) and many resources per file.

Two defects:

  1. Name ceiling applied too broadly. It should apply only to the attribute values the extractor actually REPORTS (x:Key, x:Name, x:Class, event handlers, binding paths, type names), never to geometry/data attributes it doesn't emit. A long Data string must not decline anything.
  2. Body ceiling cuts off silently. When the body ceiling is hit, the remaining facts are dropped and the code says "unsupported syntax", which misnames a size limit. Either index the whole file (paginate the response, or raise the ceiling with the response still bounded by src_offset) or report a distinct extract.truncated / extract.fact_budget_reached that names the limit. Prefer indexing in full.

Test: a synthetic resource dictionary with about 2,000 <Geometry x:Key=…> entries, each with a ~6 KB path, plus a reference to the LAST key from another file. Every key must be indexed, the last key's reference must resolve, and the diagnostic list must be empty. Mutations: restore the broad name ceiling → red; restore the silent body cut → red.

Need from the reporter, if possible: the sizes of Icons.xaml and Pie2DModels.xaml and their longest attribute value, to confirm which ceiling fired.

Field report from the TimeLine project (de.h-dv.xaml, via `resolution_gaps`), 2026-10-04. Four XAML files are only partly indexed: - `Themes/Icons.xaml` (the client's shared icon resources): `extract.unsupported_syntax` - `DevExpress.Xpf.Charts/Generic/Pie2DModels.xaml`: `extract.unsupported_syntax` - two code-generator templates / expected outputs: `extract.parse_error`. These are expected: the files contain template placeholders. **Impact:** uses of an icon key that appear after the point where extraction stopped are missing from the index. "Where is icon X defined or used" undercounts, and the agent has to fall back to search_text. **Likely cause:** `_prdoc/records/80-S12-xaml-reference-package.md` §5 describes two ceilings that emit `extract.unsupported_syntax`: - a 4,096-byte NAME ceiling on an attribute value; - a 196,608-byte response-BODY ceiling. Icon and 3D-model dictionaries hold very long geometry strings (`Data="M…"`, `Geometry`, `Points`) and many resources per file. **Two defects:** 1. **Name ceiling applied too broadly.** It should apply only to the attribute values the extractor actually REPORTS (`x:Key`, `x:Name`, `x:Class`, event handlers, binding paths, type names), never to geometry/data attributes it doesn't emit. A long `Data` string must not decline anything. 2. **Body ceiling cuts off silently.** When the body ceiling is hit, the remaining facts are dropped and the code says "unsupported syntax", which misnames a size limit. Either index the whole file (paginate the response, or raise the ceiling with the response still bounded by `src_offset`) or report a distinct `extract.truncated` / `extract.fact_budget_reached` that names the limit. Prefer indexing in full. **Test:** a synthetic resource dictionary with about 2,000 `<Geometry x:Key=…>` entries, each with a ~6 KB path, plus a reference to the LAST key from another file. Every key must be indexed, the last key's reference must resolve, and the diagnostic list must be empty. Mutations: restore the broad name ceiling → red; restore the silent body cut → red. Need from the reporter, if possible: the sizes of `Icons.xaml` and `Pie2DModels.xaml` and their longest attribute value, to confirm which ceiling fired.
Author
Member

Verified fixed and shipped. Commit f394e94f89 is an ancestor of published v0.41.34; its permanent regression is unchanged and passed again in the current native Windows timing lane (PR #490, job 60476).

Independent public-runtime check also passes using the official signed XAML 0.3.2 archive (release 769; archive SHA-256 3a4d2e0d302a24fad92cb1dbb1533a1f23746ac1a402a232158a1109049cf901) and installed 0.41.34:

  • 2,000 geometries, including 50 unreported geometry attributes of 6,000 bytes; all 4,001 resource keys and 4,000 dictionary references are indexed, and all dictionary references resolve.
  • References to the last keys from another file resolve to the exact dictionary. Binding-path and outside-directory decoys remain unbound.
  • Extraction diagnostics are measured empty. These assertions pass through both snapshot and daemon MCP transports. Normal CLI installation verifies the published signature and conformance.

The file stays under the normal 2-MiB input cap. The original 2,000 × 6-KiB suggestion produces a 12-MB input and requires an explicit index size-limit increase; the permanent test documents why it instead preserves both failure-triggering shapes under the default cap. It also records the executed negative controls: restoring the broad attribute ceiling produces unsupported_syntax; restoring the old body cutoff loses the tail and reports node_limit_reached.

The original body-truncation diagnosis was inaccurate: the unsupported_syntax came from applying the name ceiling to unreported geometry attributes. The output budget remains bounded and reports node_limit_reached when exhausted. Cross-directory merged-dictionary reachability remains a separate resolver limitation, not silently accepted by this check.

Closing with public E2E evidence, not another source change or CI run. Receipt: /tmp/cosi-312-published-e2e/report.json.

Verified fixed and shipped. Commit f394e94f89a492b05ccd48450c5223f6ed235f1f is an ancestor of published v0.41.34; its permanent regression is unchanged and passed again in the current native Windows timing lane (PR #490, job 60476). Independent public-runtime check also passes using the official signed XAML 0.3.2 archive (release 769; archive SHA-256 3a4d2e0d302a24fad92cb1dbb1533a1f23746ac1a402a232158a1109049cf901) and installed 0.41.34: - 2,000 geometries, including 50 unreported geometry attributes of 6,000 bytes; all 4,001 resource keys and 4,000 dictionary references are indexed, and all dictionary references resolve. - References to the last keys from another file resolve to the exact dictionary. Binding-path and outside-directory decoys remain unbound. - Extraction diagnostics are measured empty. These assertions pass through both snapshot and daemon MCP transports. Normal CLI installation verifies the published signature and conformance. The file stays under the normal 2-MiB input cap. The original 2,000 × 6-KiB suggestion produces a 12-MB input and requires an explicit index size-limit increase; the permanent test documents why it instead preserves both failure-triggering shapes under the default cap. It also records the executed negative controls: restoring the broad attribute ceiling produces unsupported_syntax; restoring the old body cutoff loses the tail and reports node_limit_reached. The original body-truncation diagnosis was inaccurate: the unsupported_syntax came from applying the name ceiling to unreported geometry attributes. The output budget remains bounded and reports node_limit_reached when exhausted. Cross-directory merged-dictionary reachability remains a separate resolver limitation, not silently accepted by this check. Closing with public E2E evidence, not another source change or CI run. Receipt: `/tmp/cosi-312-published-e2e/report.json`.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
h-dv/code-index#312
No description provided.