one of my backends started failing due to space ge...
# proj-automation
w
one of my backends started failing due to space getting eaten up. seems like
automation-runs
workspaces aren't getting cleaned up
m
this is also a problem we saw in the VM. Which kind of automation is? For the PR review automations we saw that the bot was always cloning the repo but never deleting it. So now in the automation script for the PR review, we clone ourself the repo at the right commit and at the end we delete it.
l
@modern-fireman-99755 mind taking that one over the line? We have a (presumably vibe-coded) community PR
Feel free to fix it
👍 1
w
I have 3 scheduled automations
c
So now in the automation script we clone ourself the repo
Alternatively, we could maybe enforce cleaning up with a hook and/or goal, and prompt 🤔 But probably it wouldn’t be worth it
m
Actually I think the issue of Graham is pretty good.
Alternatively, we could maybe enforce cleaning up with a hook and/or goal, and prompt 🤔
I'm doing something in this direction in the VM but it is not optimal. There are still leftover
aha 1
c
Also, maybe it would be good to use /tmp, not ~/.openhands
nod 2
Ideally, there should be no reason for cloning entire repos in ~/.something
Maybe it’s just me, but I admit I feel fairly strongly about it, about software that dumps a lot of stuff in user configuration directory, because it’s the kind of thing that always gets forgotten and I kinda doubt it’s expected by users
nod 1
w
yeah I agree w/ Engel
👍 1