I just want to say eveeifyeve I don't understand this double negative at all I feel not confident that I can't find a fix

Edit: let's not discuss it here

I had a build (https://hydra.nixos.org/build/320776458/nixlog/14) fail on maximum-snail.mac.nixos.org

LLVM ERROR: IO failure on output stream: No space left on device

The dotnet build system happens to print df periodically:

  DirSize Before Building runtime
  Filesystem      Size  Used Avail Use% Mounted on
  /dev/disk3s7    229G  222G  7.1G  97% /nix

I had a build (https://hydra.nixos.org/build/320776458/nixlog/14) fail on maximum-snail.mac.nixos.org

LLVM ERROR: IO failure on output stream: No space left on device

The dotnet build system happens to print df periodically:

  DirSize Before Building runtime
  Filesystem      Size  Used Avail Use% Mounted on
  /dev/disk3s7    229G  222G  7.1G  97% /nix

is this the right place to mention that?

I have a question about declarative projects.
Let's say, your project has a jobset named old-name.

You want to rename it to new-name.
When using regular non-declarative projects, you could edit the configuration of each jobset and, among other things, rename it.
But when using declarative projects, if you cange the name of the jobset from old-name to new-name, how can Hydra differentiate betwee:

• DROP jobset old-name and create new jobset new-name
• RENAME jobset old-name to new-name
  ?

The ideal would be to let users manually set the jobset's id in the spec file. Because I guess that Hydra can only rely on jobset names to differentiate them right?

I have a question about declarative projects.
Let's say, your project has a jobset named old-name.

You want to rename it to new-name.
When using regular non-declarative projects, you could edit the configuration of each jobset and, among other things, rename it.
But when using declarative projects, if you change the name of the jobset from old-name to new-name, how can Hydra differentiate betwee:

• DROP jobset old-name and create new jobset new-name
• RENAME jobset old-name to new-name
  ?

The ideal would be to let users manually set the jobset's id in the spec file. Because I guess that Hydra can only rely on jobset names to differentiate them right?