fix(store): the local object store writes atomically and keeps content types by earakely-scale · Pull Request #9 · scaleapi/agentenv-framework

fix(store): the local object store writes atomically and keeps content types

earakely-scale

and

claude

committed

97a7770

fix(store): a recorded content type names the file it describes, and a write-once put never exposes an empty object

earakely-scale

and

claude

committed

e91eea9

fix(store): a write-once put stays exclusive on a filesystem without hard links

earakely-scale

and

claude

committed

1271813

fix(store): a live writer keeps its claim, and recorded types survive a copy that keeps modification times

earakely-scale

and

claude

committed

5896423

fix(store): claim a key without hard links with a lock that dies with its holder

earakely-scale

and

claude

committed

a2d2793

fix(store): a key's bytes and type are written and read under its lock, and staged files of dead writes are swept

earakely-scale

and

claude

committed

d46296d

fix(store): a failed overwrite keeps the old type, and the sweep spares any file a live write holds

earakely-scale

and

claude

committed

1b8b548

fix(store): an overwrite that lands is never reported as failed, and a staged file that cannot be locked is cleaned up

earakely-scale

and

claude

committed

35ea9bc

Navigation Menu

Repository navigation

fix(store): the local object store writes atomically and keeps content types - #9

fix(store): the local object store writes atomically and keeps content types#9
earakely-scale merged 8 commits into
mainfrom
edgararakelyan/local-store-atomic-writes

Commits on Sep 30, 2026

fix(store): the local object store writes atomically and keeps content types

fix(store): a recorded content type names the file it describes, and a write-once put never exposes an empty object

fix(store): a write-once put stays exclusive on a filesystem without hard links

fix(store): a live writer keeps its claim, and recorded types survive a copy that keeps modification times

fix(store): claim a key without hard links with a lock that dies with its holder

fix(store): a key's bytes and type are written and read under its lock, and staged files of dead writes are swept

fix(store): a failed overwrite keeps the old type, and the sweep spares any file a live write holds

fix(store): an overwrite that lands is never reported as failed, and a staged file that cannot be locked is cleaned up