AXON-1693: add error catching for tool return parsing #1437
Conversation
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
cabella-dot
requested review from
Blastoplex,
amarg-at,
bhorai-atl,
bwieger-atlassian-com,
ccallcottstevens,
dchiew-atl,
jwang19-atlassian,
marcomura,
matt-lassian,
mattcolman,
om-ukr,
sdzh-atlassian,
sspanchenko and
teg-atlassian
as code owners
Contributor
|
The issue is ready for review, and the acceptance criteria have been met:
|
Collaborator
bwieger-atlassian-com
left a comment
bwieger-atlassian-com
left a comment
There was a problem hiding this comment.
See comment s
…fix-json-parsing-error-on-staging merge with main
marcomura
reviewed
Jan 8, 2026
jwang19-atlassian
approved these changes
Jan 9, 2026
cabella-dot
deleted the
AXON-1693-investigate-and-fix-json-parsing-error-on-staging
branch
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.
What Is This Change?
When parsing tool return messages, sometimes the streaming breaks messages resulting in the breaking of the ui
See: https://atlassian.slack.com/archives/C08HHS3DQTU/p1766020874164619
This PR add error handling for broken tool return messages and better logging
How Has This Been Tested?
Manually
Basic checks:
npm run lintnpm run test