fix: retrieve stored result from tasks/result for failed tasks#1930
Open
Christian-Sidak wants to merge 1 commit intomodelcontextprotocol:mainfrom
Open
fix: retrieve stored result from tasks/result for failed tasks#1930Christian-Sidak wants to merge 1 commit intomodelcontextprotocol:mainfrom
Christian-Sidak wants to merge 1 commit intomodelcontextprotocol:mainfrom
Conversation
When a task-augmented request reaches 'failed' status, requestStream
now calls tasks/result to retrieve and yield the actual stored result
(same as the 'completed' branch), instead of yielding a hardcoded
ProtocolError('Task <id> failed'). This matches the spec requirement
that tasks/result must return exactly what the underlying request
would have returned.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: 1e82e88 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@modelcontextprotocol/client
@modelcontextprotocol/server
@modelcontextprotocol/express
@modelcontextprotocol/fastify
@modelcontextprotocol/hono
@modelcontextprotocol/node
commit: |
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
When a task-augmented request reaches
failedterminal status,TaskManager.requestStreamwas yielding a hardcodedProtocolError(InternalError, "Task <id> failed")instead of callingtasks/resultto retrieve the actual stored result. This meant whatever the handler stored (e.g.{ isError: true, content: [...] }) was unreachable by the client.The fix mirrors the
completedcase: callthis.getTaskResult(...)and yield{ type: 'result', result }, matching the spec requirement thattasks/resultmust return exactly what the underlying request would have returned.Root cause (
packages/core/src/shared/taskManager.ts:310-312):Test plan
test/integration/test/taskLifecycle.test.tsthat:callToolStreamon a tool registered withshouldFail: true{ type: 'result' }(not{ type: 'error' })result.isError === trueandresult.contentmatches the stored failure textFixes #1922