Stop Android storage entries coming back empty after an abrupt shutdown - #5579

Merged

shai-almog merged 17 commits into

masterfrom

fix-android-storage-durability

Aug 22, 2026

Commits on Aug 21, 2026

Stop Android storage entries coming back empty after an abrupt shutdown

shai-almog
and
claude
committed
b28377d
Address review: publish failures, scratch namespace, delete/publish race

shai-almog
and
claude
committed
d480d60
Register a storage write under the same lock that cancels one

shai-almog
and
claude
committed
731413d
Fix the PMD CloseResource gate and park the EDT for batched AR event tests

shai-almog
and
claude
committed
251bcf8
Address review: multi-process sweeping, clearStorage, scratch naming, Errors

shai-almog
and
claude
committed
fc4d9d9
Address review: path escape, cross-process deletion, and sweep expiry

shai-almog
and
claude
committed
a3c5906
Address review: abandon before logging, and lock creation across processes

shai-almog
and
claude
committed
41a1dbc
Keep the lock file out of the scratch cleanup loops

shai-almog
and
claude
committed
0d2a356
Never call a vanished scratch file a successful write, and keep the handle

shai-almog
and
claude
committed
fd1ef94
A failed write must not delete the value that was already stored

shai-almog
and
claude
committed
e703d23
Leave the liveness markers alone when clearing the storage

shai-almog
and
claude
committed
69b1490
Give up the write that failed, not every write to the same entry

shai-almog
and
claude
committed
e2680be
Keep the streaming API streaming; replace the entry only for whole values

shai-almog
and
claude
committed
db1ac3e
Sweep under the lock the other processes start their writes with

shai-almog
and
claude
committed
63a28ba
Clear the liveness lock when the claim fails, and let the tidy up fail alone

shai-almog
and
claude
committed
87a517e
Keep writeObject going through a custom Storage's own streams

shai-almog
and
claude
committed
42f5ee3
Do not let the incarnation cleanup delete a write this process has open

shai-almog
and
claude
committed
44905e3

Navigation Menu

Uh oh!

Stop Android storage entries coming back empty after an abrupt shutdown - #5579

Stop Android storage entries coming back empty after an abrupt shutdown#5579
shai-almog merged 17 commits into
masterfrom
fix-android-storage-durability

Commits on Aug 21, 2026

Stop Android storage entries coming back empty after an abrupt shutdown

Address review: publish failures, scratch namespace, delete/publish race

Register a storage write under the same lock that cancels one

Fix the PMD CloseResource gate and park the EDT for batched AR event tests

Address review: multi-process sweeping, clearStorage, scratch naming, Errors

Address review: path escape, cross-process deletion, and sweep expiry

Address review: abandon before logging, and lock creation across processes

Keep the lock file out of the scratch cleanup loops

Never call a vanished scratch file a successful write, and keep the handle

A failed write must not delete the value that was already stored

Leave the liveness markers alone when clearing the storage

Give up the write that failed, not every write to the same entry

Keep the streaming API streaming; replace the entry only for whole values

Sweep under the lock the other processes start their writes with

Clear the liveness lock when the claim fails, and let the tidy up fail alone

Keep writeObject going through a custom Storage's own streams

Do not let the incarnation cleanup delete a write this process has open