Missing commit? What's going on

[joepio]

I just had a problem using the Document invite, because apparently one of the Commits is missing.

Error opening https://atomicdata.dev/invites/1?public-key=dlOABAaykKn7F5KTOYK3gOuxSiMOLzeljtNLmcnUWNs%3D
Unable to get commits for https://atomicdata.dev/document/pnf5jlv3r2f. Resource not found. Failed to retrieve locally: 'https://atomicdata.dev/commits/Ony7Xa5pm3pdQHJrXIhSu+HUrVeGuBQ7FzzbzRBJTmZclPHUah1h35lRGwqn4dAlgML+KGyGSYM8WgV1AeKQBw=='. Resource not found. Resource https://atomicdata.dev/commits/Ony7Xa5pm3pdQHJrXIhSu+HUrVeGuBQ7FzzbzRBJTmZclPHUah1h35lRGwqn4dAlgML+KGyGSYM8WgV1AeKQBw== not found

For now I've simply created a new Resource and pointed the existing invite to there, but I don't know what has caused this.

• Commits cannot be deleted by users, it is not permitted
• Commits are only indexed after they are stored (or.. are they?)

[joepio]

A possible culprit is the get_commits_for_resource function, which uses a tpf query to find all Commits. For now I can skip over missing commits, but it still begs the question how this can happen.