Dominique Martinet

> Which system are you running on? Version: 4.0.0-dev caught my eye. I originally was running this on alpine, version here was reproducing on latest git > these tests check...

hmm, so trying a bit further (I only tried ps earlier), after "fixing" ps by creating the test files in /run rm also fails because it tries to update bolt_state.db...

I _definitely_ don't want to throw db integrity here: we can do exactly the same as we're doing with the db after removing other files, odds are we'll have removed...

I'm still interested in solving this, but I still don't have a better idea than making a few specific commands ENOSPC-safe as I'm not comfortable automating growing the podman partition...

Right now we still tell any customer stuck on this to temporarily extend the filesystem if that happens; it's been rare enough that I haven't automated anything yet. Honestly I...

hmm, I recall podman stopped on first error, but in the log you gave it lists both json files so it could very well have gone ahead with the bolt.db...

The "cannot remove machine" part of the issue is a duplicate of this -- freeing up space then running rm again worked as you've illustrated in the later message where...

(not an actual fix but) I've read somewhere someone suggesting to "init" the rmfakecloud with rmapi (just push any document), you might want to try that as a workaround if...

For follow up that commit wasn't enough and this needed https://github.com/acmel/dwarves/commit/94a01bde592c555b3eb526aeb4c2ad695c5660d8.patch as well - a user on nixos reported our update broke this as I hadn't backported the second patch....

BTW is there any way to discover all valid parameters short of reading src/input/mod.rs ? `niri msg action help` could perhaps list parameter names somehow? (but I'll leave that as...