WIP: Retain native logging deliveries through disposal #9

Draft
erikinkinen wants to merge 4 commits from feature/owned-output-invocation-lifetimes into feature/production-validation-matrix
Owner

Logd retains independent native invocation owners for serial and framebuffer writes, including draining failures. Delivery attempts survive inline append, record commitment and cancellation without matching old replies by bytes or recycled IDs. Retained chunk cursors preserve completed output while ingress continues fairly.

Depends on #8. Failed deliveries retain their first error and cleanup result, then retire only their own sink obligation after positive disposal so later records can proceed.

  • Retain native owners through collection and positive disposal.
  • Preserve payload custody and chunk progress through cancellation and eviction.
  • Account for owner/result storage in the delegated arena.
  • Cover ownership and protocol behavior across supported host/native target configurations.
  • Stage the actual selected metadata and preparation helpers required by scripts/validate-rust.py and complete the original retained Cargo checks.
  • Exercise the complete release image in the VM.
Logd retains independent native invocation owners for serial and framebuffer writes, including draining failures. Delivery attempts survive inline append, record commitment and cancellation without matching old replies by bytes or recycled IDs. Retained chunk cursors preserve completed output while ingress continues fairly. Depends on [#8](https://git.erikinkinen.fi/erix/logd/pulls/8). Failed deliveries retain their first error and cleanup result, then retire only their own sink obligation after positive disposal so later records can proceed. - [x] Retain native owners through collection and positive disposal. - [x] Preserve payload custody and chunk progress through cancellation and eviction. - [x] Account for owner/result storage in the delegated arena. - [x] Cover ownership and protocol behavior across supported host/native target configurations. - [ ] Stage the actual selected metadata and preparation helpers required by scripts/validate-rust.py and complete the original retained Cargo checks. - [ ] Exercise the complete release image in the VM.
erikinkinen added this to the Alpha 1 milestone 2026-11-06 02:46:34 +01:00
Keep independent native sink owners through collection and positive retirement. Bind inline delivery to nonreused attempts, preserve retained chunk progress and payload custody during cancellation, and observe original ingress activity without borrowed buffers across waits.
fix: Retire failed deliveries without blocking later records
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 2s
CI / test (push) Failing after 21s
5fb6cbac72
Remove only the failed attempt obligation after positive native disposal and retain its original operation and cleanup errors. Preserve failed terminal barriers and prevent malformed replies from becoming replayable completed writes.
ci: Use shared development dependency profiles
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / test (push) Has been cancelled
CI / markdown (push) Has been cancelled
f973bfc5d9
Keep authored manifests on main and select coordinated providers through Integration. Resolve branches once per run, retain the frozen snapshot and helper identity as artifacts, and use shared source checks instead of copied tests and guides.
ci: Declare policy helper and output boundaries
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 6s
CI / test (push) Failing after 1m48s
90b0a3ff2f
Select a disjoint operation parent for policy evidence and explicitly identify the helper checkout excluded from original component input. Keep the complete dependency policy and existing acceptance commands.
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 6s
CI / test (push) Failing after 1m48s
This pull request is marked as a work in progress.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin 'feature/owned-output-invocation-lifetimes:feature/owned-output-invocation-lifetimes'
git switch 'feature/owned-output-invocation-lifetimes'

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch 'feature/production-validation-matrix'
git merge --no-ff 'feature/owned-output-invocation-lifetimes'
git switch 'feature/owned-output-invocation-lifetimes'
git rebase 'feature/production-validation-matrix'
git switch 'feature/production-validation-matrix'
git merge --ff-only 'feature/owned-output-invocation-lifetimes'
git switch 'feature/owned-output-invocation-lifetimes'
git rebase 'feature/production-validation-matrix'
git switch 'feature/production-validation-matrix'
git merge --no-ff 'feature/owned-output-invocation-lifetimes'
git switch 'feature/production-validation-matrix'
git merge --squash 'feature/owned-output-invocation-lifetimes'
git switch 'feature/production-validation-matrix'
git merge --ff-only 'feature/owned-output-invocation-lifetimes'
git switch 'feature/production-validation-matrix'
git merge 'feature/owned-output-invocation-lifetimes'
git push origin 'feature/production-validation-matrix'
Sign in to join this conversation.
No description provided.