8000 Fail to resolve `flake.lock` when `inputs.something.follows = ""` · Issue #71 · oxalica/nil · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Fail to resolve flake.lock when inputs.something.follows = "" #71

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ykis-0-0 opened this issue Mar 10, 2023 · 0 comments
Closed

Fail to resolve flake.lock when inputs.something.follows = "" #71

ykis-0-0 opened this issue Mar 10, 2023 · 0 comments
Labels
A-flake Area: flake related C-bug Catagory: bug

Comments

@ykis-0-0
Copy link

I have a flake with a strange dependency that references to itself, which make nil reports:

ERROR nil::server: Failed to load flake workspace: Failed to resolve flake inputs from lock file: Flake input "secret-wrapper" is not locked

However, it does work (as I expected, referencing the flake itself) in nix build, nix flake update, and nix flake metadata

The flake.nix excerpt is something like this:

{
  description = "System Configuration(s)";

  inputs = {
    nixos.url = "github:NixOS/nixpkgs/nixos-unstable";
    # ...
    secret-wrapper.follows = "";
  };

  outputs = { self, secret-wrapper ? null, ... }@inputs: {
    # ...
  };
}

And the flake.lock excerpt:

{
  "nodes": {
    /* ... */
    "root": {
      "inputs": {
        "nixos": "nixos",
        "secret-wrapper": [],
        /* ... */
      }
    },
  /* ... */
}

Finally, thanks for making nil! It's a powerful LSP which helped me a lot! 👍

@oxalica oxalica added C-bug Catagory: bug A-flake Area: flake related labels Mar 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-flake Area: flake related C-bug Catagory: bug
Projects
None yet
Development

No branches or pull requests

2 participants
0