You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We periodically prune old builds from our TUF repo server. This means that we probably are left with some treehub objects that are no longer referenced. ie - if delete target "foo" with hash 0xdeadbeef, then 0xdeadbeef could be removed from treehub. And removing that means that some of its references could be removed. kind of what git-gc does. Does treehub anything like this to help control the size of its object database/store?
The text was updated successfully, but these errors were encountered:
We periodically prune old builds from our TUF repo server. This means that we probably are left with some treehub objects that are no longer referenced. ie - if delete target "foo" with hash 0xdeadbeef, then 0xdeadbeef could be removed from treehub. And removing that means that some of its references could be removed. kind of what git-gc does. Does treehub anything like this to help control the size of its object database/store?
The text was updated successfully, but these errors were encountered: