Known Issues

CNA snapshot c1c316b9  ·  Known Issues › Known Issues home  ·  source links pinned to c1c316b9

✓

Evidence basis: source-verified at the pinned commit. Claims on this page were checked by reading the CNA source at commit c1c316b9; unless a sentence says otherwise, nothing here was built or executed. Each entry states exactly what was read and what, if anything, was executed.

This area answers one question: what is wrong with, or missing from, CNA right now? It lists only what exists at CNA commit c1c316b9. A defect that has been fixed is not listed; a deliberate design choice is not called a bug; and a shortfall of this website's documentation is not a CNA defect.

Four kinds of issue

CategoryEntriesDefinition
Bug191Existing behaviour violates an intended or documented contract.
Functional gap60Functionality is intentionally or currently incomplete or unsupported; nothing violates a contract, the contract is narrower than one might expect.
Platform limitation13A host, platform or toolchain constraint makes behaviour differ or be unavailable.
Verification gap46An implementation exists, but the evidence that it behaves correctly is insufficient.

By subsystem

SubsystemBugsGapsPlatform limitsVerification gapsTotal
Math & geometry2400226
Core & runtime1370020
Graphics & renderers25227155
Content & XNB/CNB/CNJ1420016
Models & glTF5100015
Input61108
Audio & media1540221
Storage62109
Networking & gamer services1552022
Platforms432312
Build & CI1210417
Testing & evidence3003033
Diagnostics & Inspector52029
C API & bindings31026
Documentation & release tooling4100041

How an entry gets here

  • Every entry was re-verified at the pinned commit. An earlier audit finding is a candidate, not a fact: it was checked against the source, headers, build files and tests at c1c316b9.
  • Every entry was then read a second time by a reviewer whose brief was to refute it. A reviewer could confirm, correct, narrow, reclassify, fold or remove an entry; the candidates that were dismissed earlier were re-read by reviewers told to prove the dismissal wrong, and a sample of entries was also checked by running small probes built from the pinned sources.
  • A finding is removed only on positive evidence: the fixing code and, where one exists, the test that pins it; the renderer registry that retires the affected family (its identity is refused at configure time); or the source and the XNA 4.0 or FNA reference showing that the behaviour is the documented contract. It is not removed because a TODO vanished or a subsystem was rewritten.
  • Evidence is stated per entry. Source-verified means the failure follows from code that was read at the pinned commit; it is not a run. Reproduced means something was executed for the entry and the Evidence section names exactly what. Recorded by CNA means CNA’s own recorded run says so and it was not repeated here. Inferred means it follows from the code but depends on a platform or toolchain step nobody executed. Each entry also says whether any test touches the affected area.
  • Documentation bugs are CNA’s. A comment, header or document inside the CNA repository that contradicts the code at that commit is recorded as a bug in the Documentation & release tooling subsystem; it says the text is stale, not that the code is wrong. A gap in this website is never listed.
  • Stable identifiers. CNA-BUG-### identifiers are kept from the earlier audits; new ones continue the sequence.

Machine-readable index

The same list is published as data/known-issues.json (identifier, category, subsystem, status, severity, evidence basis, source paths, detail page), pinned to c1c316b9.

What each subsystem is supposed to do is on the Deep Dives and the Verification & Known Issues guide page; how to change it safely is in the Development area.