[High Priority] - Element deletion bug?

When I try to delete an annotation element, or a group of annotation elements, it seems that the server request uses the PUT endpoint (not the DELETE endpoint) and when I refresh the page and reload the annotions, the elements still exist. My assumption is that the PUT endpoint usage is normal behavior as it tries to modify the annotation document elements attribute and not include the specific elements that I want to delete … is this correct? If so, why are the elements not deleted? Keep in mind that I get a status 200 response (i.e. success) to the request. This behavior has been happening since the last update with the new Docker image.

I have recorded this behavior in developer mode in the video below: https://drive.google.com/file/d/1l7dhrnUuoimR2jwagv0k5oSui96GFa8C/view?usp=sharing

@dgutman Do you happen to know if Styx has any weird behavior recently?

[manthey]

@dgutman I’ve just pushed a branch to large_image called ‘old-annotations-2.x’ that adds some maintenance endpoints. GET annotation/old takes an age in days and a number of history states, and returns how many annotation history states are older than that. The companion DELETE endpoint will remove old annotation history and compact the database. DELETE won’t let you delete anything active or younger than 7 days. You should be able to cherry pick that branch to whatever version you are running to at least see what the GET endpoint reports.

[cooperlab]

I have encountered this before too when making our tutorial video. I could not identify a pattern but in doing a lot of takes I noticed that occasionally annotation elements that I deleted through the UI were re-appearing.