FA-99179 / Checkpoint tensor mapping / Member archive
Checkpoint mapping: optional buffers are treated as required parameters · case 04
optional buffers are treated as required parameters.
Case contract
Report missing required names and unexpected incoming names; optional expected names may be absent.
Why this case matters
A bounded offline model of checkpoint tensor bookkeeping in a training workflow.
One recorded failure
Sample boundary fixtureThis sample comes from the broken implementation of a controlled reproducer.
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| optional incoming | [[], ["b"]] | [[], []] | Failed |
MEMBER ARCHIVE
The complete case is available to members.
This record includes three runnable implementations, regression fixtures, execution results, and source hashes.
Member access is invitation-based. Sign in with your invited account to inspect the sources.
Sign in to the archive ↗