Repository navigation
Fix rejected Linq authorization connection links - #154
Merged
Merged
Conversation
This branch was successfully deployed
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
1 participant
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.
Production Link authorization prompts were rejected with HTTP 400 because Linq requires a native link to be the only part in its message. Eve swallowed the delivery error, leaving the conversation paused without its connection prompt.
Send the instruction text and native connection link as separate messages, each with its own stable idempotency key. Retain the text message ID for authorization completion updates. The regression now enforces Linq's actual message-part constraint and fails against the original implementation.
Validation:
pnpm check(777 tests, all six tasks),pnpm build, andpnpm exec eve buildpassed. The focused Linq suite passed 36 tests; independent read-only review found no issues. Live production delivery has not yet been exercised.Follow-up to #153.