tree 019331d212aa4ef2bda47b5933a23d7a43cf9a45
parent dbc4eed6f8f2455a6146da8567177de511feba8d
author Antonio Barone <syntonyze@gmail.com> 1754075652 +0300
committer Antonio Barone <syntonyze@gmail.com> 1754322063 +0300

Fix rollback implementation

When executing the rollback of a newly created ref due to a global-refdb
failure or misalignment, the global-refdb might have persisted loose
refs pointing to the zero-id rather than removing the ref itself.

Add a logic in the rollback strategy that checks whether the new
objectId is the zeroId and perform a delete instead.

Bug: Issue 435473094
Change-Id: Ieff087d27b4e361ab6310fa611c79c733455232f