Skip to content

[GP1-S3] Filesystem Runtime WAL Failure Atomicity #556

Description

@flyingrobots

Roadmap slice: GP1-S3
Goalpost: Goalpost 1: Durable Runtime WAL Join
Parent: #521
Related: #510, #518

Source: docs/design/wal-wsc-durability-roadmap.md on branch cycle/521-wal-wsc-storage-relationship at bde7957c.

Scope

Parent issues:
#510,
#518.

Scope:

  • Inject filesystem WAL append/flush/manifest failures around submission and
    tick boundaries.
  • Prove failed WAL commits roll back app-visible submission intake or tick
    outcome publication.

Acceptance:

  • A failed pre-ACK submission WAL commit leaves no witnessed submission visible.
  • A failed scheduler tick WAL commit leaves no receipt correlation or applied
    outcome visible.
  • Multi-head tick failure rolls back every tick record from the attempted
    scheduler pass.

Witness:

cargo test -p warp-core --features "native_rule_bootstrap trusted_runtime host_test" --test trusted_runtime_host_loop_tests filesystem_runtime_wal_failure

Dedupe note

This is the PR-sized implementation slice for the roadmap item above. Existing umbrella or adjacent issues remain linked as Parent/Related rather than duplicated here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    Status
    Done

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions