FROSADO / onecloudriver / 32079609151

78%

main: 78%

Build Type

Pull #102

github

Committed by FROSADO

Commit Message

fix(fs): apply root-level delta changes (canonicalize the drive root ID)

Graph delta items reference the drive root by its real item ID (e.g.
"DF54...!sea8cc...") in parentReference, while the InodeCache stores the root
inode under graph.RootID ("root"). applyDelta's parent lookup therefore
missed and root-level changes (create/edit/delete/rename at the drive root)
were silently skipped as "parent not in cache" — in the mount's delta loop
and in the manual `onecloudriver sync` command (#73).

- delta.go: new resolveParentID maps the real root ID to "root" for the
  cache lookup. The real ID is learned at most once from (a) the delta root
  item itself when present in the cycle (free, no network), or (b) a lazy
  GetItem(root) on the first parent miss (sync.Once, fails gracefully, at
  most one extra call per DeltaSync lifetime) — so cycles carrying only a
  root-level edit (no root item) also apply.
- The delta root item now also refreshes the cached root's folder metadata
  (childCount) and persists it as dirty.
- Tests: applyDelta root-level new item (ID learned from the root item),
  root-level content change (ID learned via lazy GetItem), and an end-to-end
  pollAndApply cycle [root item, root-level file] (the #73 scenario). The
  BoundedMemory mock is now path-aware so the lazy GetItem
  (/me/drive/root) answers 404 without consuming a delta page slot. All
  three fail against the pre-fix code.

Closes #101

Pull Request Pull Request #102: fix(fs): apply root-level delta changes (canonicalize the drive root ID)

Coverage Stats

37 of 37 new or added lines in 1 file covered. (100.0%)

2 existing lines in 1 file now uncovered.

4457 of 5694 relevant lines covered (78.28%)

3463.76 hits per line