You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
calling tool multiple times can cause the json file to become corrupted due to writing malformed data
To Reproduce
Steps to reproduce the behavior:
trigger multiple calls to Memory from a single LLM response (e.g. create entity, delete observation, add observation, and create relation)
Expected behavior
It should not be possible for the tool to write corrupted data to fle.
Ideally, it would correctly handle concurrent writes to ensure atomic operations
minimally, it would validate any data before being written, to ensure that malformed data is not saved and it fails gracefully.
Additional context
Currently This has to be resolved manually every time, once the file is corrupted it is not possible for the tool to recover/fix by itself, every operation fails
The text was updated successfully, but these errors were encountered:
Describe the bug
calling tool multiple times can cause the json file to become corrupted due to writing malformed data
To Reproduce
Steps to reproduce the behavior:
trigger multiple calls to Memory from a single LLM response (e.g. create entity, delete observation, add observation, and create relation)
Expected behavior
It should not be possible for the tool to write corrupted data to fle.
Ideally, it would correctly handle concurrent writes to ensure atomic operations
minimally, it would validate any data before being written, to ensure that malformed data is not saved and it fails gracefully.
Additional context
Currently This has to be resolved manually every time, once the file is corrupted it is not possible for the tool to recover/fix by itself, every operation fails
The text was updated successfully, but these errors were encountered: