Describe the bug
In the cube commit route, Cobra writes updates to DB first, then writes the changelog. If the server fails between these two events, Cobra has no way to reconcile that missing history
To Reproduce
Steps to reproduce the behavior:
Call /cube/soskgy/commit with a change et
Kill server after this line runs but before the next one.
See updated cube with missing history
Expected behavior
I want the changelog to be the ultimate source of truth for the current state of the cube. Once a single update has a missed history it becomes much harder to rebuild the state of the cube from the existing data.
Describe the bug In the cube commit route, Cobra writes updates to DB first, then writes the changelog. If the server fails between these two events, Cobra has no way to reconcile that missing history
To Reproduce Steps to reproduce the behavior:
/cube/soskgy/commit
with a change etExpected behavior I want the changelog to be the ultimate source of truth for the current state of the cube. Once a single update has a missed history it becomes much harder to rebuild the state of the cube from the existing data.