5
11
Fork
You've already forked tomato
1

Remove ActiveSnapshot #107

Merged
edwardloveall merged 1 commit from el-remove-active-snapshot into main 2026年03月05日 17:13:43 +01:00

In a217ebe7 and 99ba41d8, I added functionality to track changes to events and
shifts. It works okay, but it turned out to be actually really difficult to see
the differences we cared about. Part of it is how we added and removed tasks
instead of updating the list, part of it was because of how we split events.
Over the course of the two months it's been installed, I haven't been able to
use it to find anything useful.

On top of that, it takes up the most space by a couple orders of magnitude. in
our database and grows very quickly. I looked into reducing what it stores, but
I wasn't confident that it would help instead of hinder the debugging process.
And since then I added HttpRequest logging (e4d3a589) which has already helped
find one bug in less than a month and takes up far less space.

In a217ebe7 and 99ba41d8, I added functionality to track changes to events and shifts. It works okay, but it turned out to be actually really difficult to see the differences we cared about. Part of it is how we added and removed tasks instead of updating the list, part of it was because of how we split events. Over the course of the two months it's been installed, I haven't been able to use it to find anything useful. On top of that, it takes up the most space by a couple orders of magnitude. in our database and grows very quickly. I looked into reducing what it stores, but I wasn't confident that it would help instead of hinder the debugging process. And since then I added HttpRequest logging (e4d3a589) which has already helped find one bug in less than a month and takes up far less space.
Remove ActiveSnapshot
All checks were successful
ci/woodpecker/pr/ci Pipeline was successful
ebfc7bc8ab
In a217ebe7 and 99ba41d8, I added functionality to track changes to events and
shifts. It works okay, but it turned out to be actually really difficult to see
the differences we cared about. Part of it is how we added and removed tasks
instead of updating the list, part of it was because of how we split events.
Over the course of the two months it's been installed, I haven't been able to
use it to find anything useful.
On top of that, it takes up the most space by a couple orders of magnitude. in
our database and grows very quickly. I looked into reducing what it stores, but
I wasn't confident that it would help instead of hinder the debugging process.
And since then I added HttpRequest logging (e4d3a589) which has already helped
find one bug in less than a month and takes up far less space.
jsilasbailey left a comment
Copy link

Good call on backing out, also seems fairly easy so overall a good experiment to run 👍

Good call on backing out, also seems fairly easy so overall a good experiment to run 👍
edwardloveall deleted branch el-remove-active-snapshot 2026年03月05日 17:13:50 +01:00
Sign in to join this conversation.
No reviewers
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
rootable/tomato!107
Reference in a new issue
rootable/tomato
No description provided.
Delete branch "el-remove-active-snapshot"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?