Fix scratch pad when return_history is true #4310
Merged
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.
Description
During testing, there is casting exception when multiple writes to scratch pad when return_history is true, because we need to parse input notes from string, process as List, store back as JSON string.
Solution
Modified both ReadFromScratchPadTool and WriteToScratchPadTool to:
Key Changes
• ReadFromScratchPadTool: Parse input notes from string, process as List, store back as JSON string
• WriteToScratchPadTool: Parse existing notes from string, append new note, store as JSON string
• Updated Tests: Fixed all unit tests to expect JSON string format and added specific string conversion test cases
###Verifying after fix:
GET {{host}}/_plugins/_ml/memory/message/xgdl4JkBjTTL2aEw_BNV/traces?next_token=0
Check List
--signoff
.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.