`exportReferencesGraph` started including a `valid: true` field

[flokli]

`exportReferencesGraph` started including a `valid: true` field

[Kranzes]

Potentially caused by #9242

[flokli]

That PR description even mentions the stability in structured attrs:

This keeps the human oriented CLI logic (which is currently stable) and the core domain logic (export reference graphs with structured attrs, which is stable), separate, which I think is better.

[tomberek]

New output has a "valid" field.

  {
    "closureSize": 2216152,
    "narHash": "sha256:0z1mdik09afiskvxjzcxl60sq0rzvh7lx6a7hxs2q1s379r6n1n5",
    "narSize": 358784,
    "path": "/nix/store/w4djxksksd1p8m054k537plqnif5858k-libidn2-2.3.4",
    "references": [
      "/nix/store/4r64z7v5l40pg6r0hd169bcs85c8c42b-libunistring-1.1",
      "/nix/store/w4djxksksd1p8m054k537plqnif5858k-libidn2-2.3.4"
    ],
    "valid": true
  }

Perhaps just:

diff --git a/src/libstore/parsed-derivations.cc b/src/libstore/parsed-derivations.cc
index 72f45143d..09801919f 100644
--- a/src/libstore/parsed-derivations.cc
+++ b/src/libstore/parsed-derivations.cc
@@ -151,8 +151,6 @@ static nlohmann::json pathInfoToJSON(
         // Add the path to the object whose metadata we are including.
         jsonPath["path"] = store.printStorePath(storePath);

-        jsonPath["valid"] = true;
-
         jsonPath["closureSize"] = ({
             uint64_t totalNarSize = 0;
             StorePathSet closure;