Commit 358fa87
committed
fix(workspace): archiveNow reads through fetchKnownRecords, warns on truncation
`archiveNow` was calling `MemoryApi.list()` directly. Once a workspace has
>= LIST_LIMIT records and the block the user wants to delete is beyond
that window, the `records.find(...)` fallback returns undefined, the
`if (!current) return` branch takes it silently, and the block stays
live in the cloud — every later session re-injects it with no diagnostic
trace.
Route the read through `fetchKnownRecords()` (same as `push`), and log a
warning on the truncated-no-find path so the failure mode is at least
observable. Small semantics: a "not truncated + not found" no-op is still
correct (the block genuinely isn't there); the warning only fires when
truncation is the plausible explanation. (altimate-harness-bot #1116
comment 3841102064.)1 parent f6b8c32 commit 358fa87
1 file changed
Lines changed: 19 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
505 | 505 | | |
506 | 506 | | |
507 | 507 | | |
508 | | - | |
509 | | - | |
510 | | - | |
511 | | - | |
| 508 | + | |
| 509 | + | |
| 510 | + | |
| 511 | + | |
| 512 | + | |
| 513 | + | |
| 514 | + | |
512 | 515 | | |
513 | 516 | | |
514 | 517 | | |
| |||
524 | 527 | | |
525 | 528 | | |
526 | 529 | | |
527 | | - | |
| 530 | + | |
| 531 | + | |
| 532 | + | |
| 533 | + | |
| 534 | + | |
| 535 | + | |
| 536 | + | |
| 537 | + | |
| 538 | + | |
| 539 | + | |
| 540 | + | |
| 541 | + | |
528 | 542 | | |
529 | 543 | | |
530 | 544 | | |
| |||
0 commit comments