Repository navigation
fix(openclaw): bound media hydration and preserve existing attachments - #140
Merged
Merged
Conversation
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
A successful verdict POST could still leave the final reply waiting indefinitely on the image GET or body. Carry the existing request AbortSignal through hydration, and preserve existing single and multiple attachments when adding emotion media. Covers F04/F16.
Includes separate stalled-header and stalled-body regressions and a single-attachment preservation case. This PR is independent of the watcher delivery proposal; #137 touches the same entrypoint and may require a rebase when merged.
Verification
dev(da2120e).git diff --checkpassed.node scripts/release-gate.mjs— full release gate and real gateway replacement E2E were not run; no release-readiness claim.Architecture Boundary
OpenClaw remains a thin media adapter with no new classifier, profile, asset lookup, or direct Discord REST. Changeset Validation requires owner review because openclaw/index.ts changes; no approval or owner-reviewed label is asserted.
Part of the September 8 functional audit split. Security vulnerability investigation and reproduction are outside this work. All split PRs target
dev; there is no stacked branch dependency.