fails to initialize project on nixos

[Briaoeuidhtns]

Component

c/v3-cli

What is the current behaviour?

When running init via the ddn flake it exits with an error:

$ nix run github:hasura/ddn-cli-nix -- supergraph init test
4:50PM ERR failed to get compatibility config date: exit status 127

The folder, if it didn't exist, and any files, are not created.

What is the expected behaviour?

Command should run successfully and init a new project

How to reproduce the issue?

1. Run nix run github:hasura/ddn-cli-nix -- supergraph init test on nixos (I'm on 25.05pre775060.5e5402ecbcb2 (Warbler))

Please provide any traces or logs that could help here.

Running with debug logging, env vars omitted

4:49PM DBG global config directory is not pre-set, defaulting
4:49PM DBG global config directory set as '/home/brian/.ddn'
4:49PM DBG global config file set as '/home/brian/.ddn/config.yaml'
4:49PM DBG global config file exists, verifying contents
4:49PM DBG global config is not pre-set, reading from current env
4:49PM DBG global config: uuid: 30504a66-5c7e-4727-97c0-9867a9b17419
4:49PM DBG global config: enableTelemetry: true
4:49PM DBG global config: showUpdateNotification: true
4:49PM DBG global config: cliEnvironment: default
4:49PM DBG execution id: bf65e3ac-0d79-415f-b7f6-9baf500ea601
4:49PM DBG Executing the command Command="/run/current-system/sw/bin/bash -c ddn-iteration764108854 compatibility-config-date"

Any possible solutions/workarounds you're aware of?

no

[robertjdominguez]

Thanks, @Briaoeuidhtns — I'm tagging one of the authors of this repo: hasura/ddn-cli-nix. I'm not very sure how maintained that particular repository is.

@hallettj — can you please comment or triage?

[Briaoeuidhtns]

is there a more supported way to run ddn on nixos? I get the same thing installing via the pipe to bash command in the docs

I also tried to look into it myself but the nix flake just pulls a blob. is the source available for the ddn cli tool?

[hallettj]

Hi @Briaoeuidhtns! The flake you're running from is the best we've got for nixos packaging. You're right, all it does is to fetch a precompiled binary, which is the same binary that we ship to other systems. And it looks like there is an issue with the stock binary with that fact than nix doesn't use an FHS. I put this together mostly for my own use so I'm afraid it ended up in a "good enough for now" state. If I get some time I may be able to update the flake to wrap the binary with buildFHSUserEnv which may fix things.

In the meantime running from the flake does work if you have nix-ld set up. That's a shim that allows running lots of precompiled binaries on nixos without special packaging. If it's ok for your situation there's a one-liner you can add to your nixos configuration to turn it on:

programs.nix-ld.enable = true;

Edit: Sorry, I didn't answer the last part of your comment. No, the cli tool is not open source. That makes it trickier to write a proper nix expression that would link everything correctly. That's why I'm looking at the perspective of a user FHS. Or there might be something I can do with patchElf.