Serious bug in 0.5.5 with update... it doesn't

[LStromann]

=I've been experimenting with openclaw and the cognee integration and as part of my debugging I wrote myself a quick frontend to be able to view/query the data within the dataset and what I found was a little alarming in that sync is syncing files and updating data, you can see the updated_at timestamp change but if you read the data back then it has not been updated, the original raw file data is still returned. I've put together a shell script that demonstrates it with a dataset and single file with some random data and a version number, despite the update being accepted then the version 1 file is still returned.
So the question is, is it my method if so then what am I doing wrong and if not then its a pretty serious bug.
#2449
Test script to reproduce is attached to the issue report and to this post.

This discussion was automatically pulled from Discord.

[LStromann]

I don't think the updated file has the same data_id as the original, can you check what data with what ID is in the dataset?

To me the issue seems more likely to be that we don't actually clean every part of the old data (specifically only the raw text from old data remains), but the graph/vector and relational store and Cognee itself in general doesn't use the old data