WIP: Retain original owned stream invocation custody #29
No reviewers
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/sha2-tool!29
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/owned-stream-invocation-custody"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Keep the native hash tool's invocation row and separate original request/result packets outside platform and transport wrappers. Retain their complete execution lifetime through positive retirement or fail-stop, using the startup-bound owned stream adapter.
Supports native SHA-2 execution. All Cargo declarations continue to track main; shared companion profiles select the coordinated development branches.
The native receiver must already be explicitly registered. Native retirement concerns invocation custody; it does not attest provider rollback or application teardown.
The manual inventory binds the updated native entry source, so offline manual packaging validates the same owned stream implementation.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.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.