summaryrefslogtreecommitdiff
path: root/vendor/golang.org/x/sys/unix/syscall_darwin_libSystem.go
diff options
context:
space:
mode:
authorJacob Weisz <ocdtrekkie@noreply@mills.io>2024-03-16 05:44:51 +0000
committerJames Mills <james@mills.io>2024-03-16 05:44:51 +0000
commit0f4ee60246f918a8a704a7e8a726a948b93f2999 (patch)
treefb2827562a913ddb212b243bce7b78d569057eac /vendor/golang.org/x/sys/unix/syscall_darwin_libSystem.go
parent5e0946bf326c3ff5869cc0c2da94e4d6761d6475 (diff)
Sandstorm: Clean up uploads (#73)
So one issue I've found is that sometimes Sandstorm will kill a grain while it is still transcoding (on my todo list, figure out how to lock the grain open during transcoding...). When that happens, a tube-transcode- and tube-upload- file each get left behind in the uploads directory. If I understand this correctly, tube should never look for those files again, and they are just storage waste. In the case of a grain I made today, the uploads directory remains half the grain's size, even though the actual videos tube serves are elsewhere. So I believe that I wrote this correctly, but haven't tested it yet: When launching the Sandstorm grain, we should just dump the contents of the uploads directory to clean up unusable data. Reviewed-on: https://git.mills.io/prologic/tube/pulls/73 Reviewed-by: James Mills <james@mills.io> Co-authored-by: Jacob Weisz <ocdtrekkie@noreply@mills.io> Co-committed-by: Jacob Weisz <ocdtrekkie@noreply@mills.io>
Diffstat (limited to 'vendor/golang.org/x/sys/unix/syscall_darwin_libSystem.go')
0 files changed, 0 insertions, 0 deletions