Cover owned framebuffer reply correlation #48
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/ttyd!48
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/owned-framebuffer-reply-controls"
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?
Exercise a real prepared renderer request through owned framebuffer submission, collection and release, then the existing reply-body parser. A mismatched response request ID must leave the original output queued while releasing that same invocation exactly once.
The connected control preserves the existing body-level correlation contract. Depends on #47 and extends the failure coverage tracked in #46.
WIP: Cover owned framebuffer reply correlationto Cover owned framebuffer reply correlationPrepared the merge history at 7ab77d2e to remove duplicate upstream patches and integrate the feature on its prepared prerequisite history. The feature tree is unchanged.