List changes after a sequence
Returns committed changes from the write-ahead log. Callers can use this feed to keep another projection synchronized with WAL history.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Namespace id
Query Parameters
Section titled “Query Parameters ”Return committed changes after this sequence
Maximum page size
Responses
Section titled “ Responses ”Committed changes
Change-feed response after a cursor.
object
Exclusive cursor supplied by the caller, or the endpoint’s initial position.
Logical commits after after_seq, ordered by ascending namespace sequence.
One committed change in namespace order.
object
Client idempotency key for this logical commit.
Wall-clock stamp of the commit, in Unix milliseconds.
Observational: seq is the order.
Semantic filesystem events, one per committed operation, in request-operation order.
A file or directory was created.
object
Content of the first revision, for file creations.
object
Immutable identity of the referenced object.
Content strategy used by the referenced object.
Complete byte length of the referenced content.
Mandatory checksum over the complete object, used to verify the stored bytes against this reference without downloading them.
object
Algorithm that produced value.
Lowercase hex of the raw checksum bytes.
The algorithm is its own field, so the value carries no prefix. Provider APIs that report base64 are converted at the adapter.
SHA-256 over the complete payload, lowercase hex, when a trusted party computed it.
Present means the LoonFS write path hashed the whole stream itself, or a provider validated a signed whole-object SHA-256 on the write. There are no client-claimed digests: absent means nobody trustworthy hashed these bytes, never “the client did not tell us”.
Newly allocated namespace-scoped inode identity.
File-or-directory classification fixed at creation.
User-facing spelling of the new entry.
Directory the new entry was bound under.
A file received a new current revision — a put over an existing file, or a revision restore (one durable fact for both).
object
Immutable content published by the revision.
object
Immutable identity of the referenced object.
Content strategy used by the referenced object.
Complete byte length of the referenced content.
Mandatory checksum over the complete object, used to verify the stored bytes against this reference without downloading them.
object
Algorithm that produced value.
Lowercase hex of the raw checksum bytes.
The algorithm is its own field, so the value carries no prefix. Provider APIs that report base64 are converted at the adapter.
SHA-256 over the complete payload, lowercase hex, when a trusted party computed it.
Present means the LoonFS write path hashed the whole stream itself, or a provider validated a signed whole-object SHA-256 on the write. There are no client-claimed digests: absent means nobody trustworthy hashed these bytes, never “the client did not tell us”.
File inode whose history advanced.
New monotonic position in that file’s revision history.
An inode moved to a new parent directory or name.
object
Spelling of the old binding.
Directory that held the old binding.
Inode whose binding changed.
Spelling of the new binding.
Directory holding the new binding.
A file or directory subtree was deleted. The enclosing change’s
seq is the deletion generation an undelete request passes as
deleted_at_seq.
object
Inode at the root of the deleted subtree.
A deleted inode was recovered and re-bound.
object
Recovered inode.
Spelling of the recovered binding.
Directory the recovered entry was bound under.
Caller annotation, omitted when absent and carrying no filesystem semantics.
Namespace sequence for this logical commit.
Namespace whose ordered commit stream was read.
Snapshot head through which this page was evaluated.
Invalid change cursor or limit
HTTP error body used by LoonFS APIs.
object
Stable machine-readable reason from the ErrorCode
registry.
Carried as a string so clients keep working when a newer server
introduces a code they do not know; use
ErrorCode::parse for typed access.
Structured context for the code, present when the failure carries machine-usable identity (API spec, “Standard error contract”). Boxed so the rare detailed error does not widen every error-carrying result.
object
Unix milliseconds at which the current epoch’s acquirer took it, when the head recorded one. Writer ids are process labels, so two runs on one machine can share one; the stamp is what tells them apart.
Writer id recorded by the current epoch’s acquirer, when the head recorded one.
Sequence at which that commit id already landed. Present when the failure was decided against a durable commit receipt, which is what holds the sequence; absent when nothing has committed under the id yet and two live requests are simply claiming it at once.
Position, in the request’s operation list, of the operation that failed. A commit applies all of its operations or none of them, so this names the one that stopped the whole request.
For not_supported errors, the capability-document feature key the
client should reconcile against.
Human-readable error message.
Correlation id the server assigned to the failed request; the same
value is sent as the x-request-id response header.
Unauthorized
HTTP error body used by LoonFS APIs.
object
Stable machine-readable reason from the ErrorCode
registry.
Carried as a string so clients keep working when a newer server
introduces a code they do not know; use
ErrorCode::parse for typed access.
Structured context for the code, present when the failure carries machine-usable identity (API spec, “Standard error contract”). Boxed so the rare detailed error does not widen every error-carrying result.
object
Unix milliseconds at which the current epoch’s acquirer took it, when the head recorded one. Writer ids are process labels, so two runs on one machine can share one; the stamp is what tells them apart.
Writer id recorded by the current epoch’s acquirer, when the head recorded one.
Sequence at which that commit id already landed. Present when the failure was decided against a durable commit receipt, which is what holds the sequence; absent when nothing has committed under the id yet and two live requests are simply claiming it at once.
Position, in the request’s operation list, of the operation that failed. A commit applies all of its operations or none of them, so this names the one that stopped the whole request.
For not_supported errors, the capability-document feature key the
client should reconcile against.
Human-readable error message.
Correlation id the server assigned to the failed request; the same
value is sent as the x-request-id response header.
Namespace not found
HTTP error body used by LoonFS APIs.
object
Stable machine-readable reason from the ErrorCode
registry.
Carried as a string so clients keep working when a newer server
introduces a code they do not know; use
ErrorCode::parse for typed access.
Structured context for the code, present when the failure carries machine-usable identity (API spec, “Standard error contract”). Boxed so the rare detailed error does not widen every error-carrying result.
object
Unix milliseconds at which the current epoch’s acquirer took it, when the head recorded one. Writer ids are process labels, so two runs on one machine can share one; the stamp is what tells them apart.
Writer id recorded by the current epoch’s acquirer, when the head recorded one.
Sequence at which that commit id already landed. Present when the failure was decided against a durable commit receipt, which is what holds the sequence; absent when nothing has committed under the id yet and two live requests are simply claiming it at once.
Position, in the request’s operation list, of the operation that failed. A commit applies all of its operations or none of them, so this names the one that stopped the whole request.
For not_supported errors, the capability-document feature key the
client should reconcile against.
Human-readable error message.
Correlation id the server assigned to the failed request; the same
value is sent as the x-request-id response header.
Namespace deleted
HTTP error body used by LoonFS APIs.
object
Stable machine-readable reason from the ErrorCode
registry.
Carried as a string so clients keep working when a newer server
introduces a code they do not know; use
ErrorCode::parse for typed access.
Structured context for the code, present when the failure carries machine-usable identity (API spec, “Standard error contract”). Boxed so the rare detailed error does not widen every error-carrying result.
object
Unix milliseconds at which the current epoch’s acquirer took it, when the head recorded one. Writer ids are process labels, so two runs on one machine can share one; the stamp is what tells them apart.
Writer id recorded by the current epoch’s acquirer, when the head recorded one.
Sequence at which that commit id already landed. Present when the failure was decided against a durable commit receipt, which is what holds the sequence; absent when nothing has committed under the id yet and two live requests are simply claiming it at once.
Position, in the request’s operation list, of the operation that failed. A commit applies all of its operations or none of them, so this names the one that stopped the whole request.
For not_supported errors, the capability-document feature key the
client should reconcile against.
Human-readable error message.
Correlation id the server assigned to the failed request; the same
value is sent as the x-request-id response header.