Skip to content

merge queue: checking #811 on main (41a11e8) - #855

Closed
mergify[bot] wants to merge 10 commits into
mainfrom
mergify/merge-queue/0b32c8409c
Closed

mergify[bot] wants to merge 10 commits into
mainfrom
mergify/merge-queue/0b32c8409c

Conversation

@mergify

@mergify mergify Bot commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

🎉 This pull request has been checked successfully and will be merged soon. 🎉

#811 is queued for merge on branch main (41a11e8).

This pull request has been created by Mergify to check the mergeability of #811.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

  • check-success = gates (linux)
  • check-success = gates (windows)
  • check-success = red-first
  • github-review-approved [🛡 GitHub repository ruleset rule main-pr-required-checks]
  • label != do-not-merge
  • all of [🛡 Merge Protections rule Paket-PR bringt seinen Bericht mit]:
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-success = @github-actions/gates (linux)
    • check-neutral = @github-actions/gates (linux)
    • check-skipped = @github-actions/gates (linux)
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-success = @github-actions/gates (windows)
    • check-neutral = @github-actions/gates (windows)
    • check-skipped = @github-actions/gates (windows)
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-success = @github-actions/red-first
    • check-neutral = @github-actions/red-first
    • check-skipped = @github-actions/red-first
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-neutral = @mergify/Mergify Merge Protections
    • check-skipped = @mergify/Mergify Merge Protections
    • check-success = @mergify/Mergify Merge Protections

Required conditions to stay in the queue:

---
all_scopes: false
checking_base_sha: 41a11e810ad640963c6c4e3e8cf9a1790fe8b799
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 811
    scopes: []
scopes: []
...

Cuarroc and others added 10 commits October 9, 2026 04:24
Introduce a standalone Option-A ownership module with O_EXCL create,
nonce-checked release, and fail-closed stale/malformed refusal before
core/server wiring.

Test-First: tools/denkraum/store/ownership.test.mjs::DRSEC: second process is refused while ownership is held
Test-First: tools/denkraum/store/ownership.test.mjs::DRSEC: same-process second acquire with a different nonce is refused
Test-First: tools/denkraum/store/ownership.test.mjs::DRSEC: stale heartbeat does not release ownership
Test-First: tools/denkraum/store/ownership.test.mjs::DRSEC: malformed owner record fails closed
Test-First: tools/denkraum/store/ownership.test.mjs::DRSEC: release with foreign nonce keeps the record
Test-First: tools/denkraum/store/ownership.test.mjs::DRSEC: owner record is created exclusively with mode 0600
Co-authored-by: Cursor <cursoragent@cursor.com>
Overlapping release with the same nonce no longer deletes a successor's
owner record: release is single-flight per nonce and unlinks only after a
verified tombstone rename.

Test-First: tools/denkraum/store/ownership.test.mjs::DRSEC: overlapping release cannot unlink a successor record
Co-authored-by: Cursor <cursoragent@cursor.com>
…IP_IO

Acquire and release normalize open/read/rename/unlink failures to a fixed
OwnershipError code without attaching the raw cause or any path fragment.

Test-First: tools/denkraum/store/ownership.test.mjs::DRSEC: filesystem failures use fixed diagnostics without paths
Co-authored-by: Cursor <cursoragent@cursor.com>
…ilure

When wx create succeeds but the initial write/flush fails, the creator
unlinks its own incomplete record and returns a fixed OWNERSHIP_IO error.

Test-First: tools/denkraum/store/ownership.test.mjs::DRSEC: failed write after create removes the half-written record
Co-authored-by: Cursor <cursoragent@cursor.com>
…n close

Register child cleanup immediately after spawn, join with a deadline on
every path, and make the contender fixture exit non-zero if stdin closes
without an explicit release.

Test-First: tools/denkraum/store/ownership.test.mjs::DRSEC: fixture exits non-zero when stdin closes without release
Co-authored-by: Cursor <cursoragent@cursor.com>
Pins the missing-record release path to OWNERSHIP_RELEASE_MISMATCH with
path-free diagnostics (GLM F1).

Test-First: tools/denkraum/store/ownership.test.mjs::DRSEC: release of a missing record is a fixed mismatch
Co-authored-by: Cursor <cursoragent@cursor.com>
Unique per-release tombstones and exclusive link restore prevent a stale
cross-instance release from overwriting a live successor (R811-O5).

Test-First: tools/denkraum/store/ownership.test.mjs::DRSEC: cross-instance stale release never overwrites a live owner
Co-authored-by: Cursor <cursoragent@cursor.com>
No-Test: documentation of the accepted API precondition and an honest test name (Elias E6b)
Co-authored-by: Cursor <cursoragent@cursor.com>
No-Test: documentation of the accepted API precondition and an honest test name (Elias E6b)
Co-authored-by: Cursor <cursoragent@cursor.com>
@mergify mergify Bot closed this Oct 9, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/0b32c8409c branch October 9, 2026 13:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant