this derivation will be built: /nix/store/5wcnsbxndhnjl9vaimixzn8gliw1mxf2-iets-ast-grep.drv error: build of '/nix/store/5wcnsbxndhnjl9vaimixzn8gliw1mxf2-iets-ast-grep.drv' on 'grpc://farm.numtide.com:50051?connect-timeout=20&system=aarch64-linux&token-file=/run/nix-farm-client/farm-token' failed: Cannot build '/nix/store/5wcnsbxndhnjl9vaimixzn8gliw1mxf2-iets-ast-grep.drv'. Reason: builder failed with exit code 1. Output paths: /nix/store/7ghag4ad96q5nkxg0iw6xl9z33sk3pr9-iets-ast-grep Last 25 log lines: > │ > 184 │ ╭ /// the path resolution ended at, and its place in the (virtual) store, `None` > 185 │ │ ╭ /// for one the real file system answers. [`resolve_links`] runs under a store > │ ╰────────────' > 186 │ │ ╭ /// path this evaluation copied from a local tree, and in a pure evaluation > │ ╰──────────' > 187 │ │ ╭ /// under the project: there the kernel would follow a link out of the allow > │ ╰────────' > 188 │ │ ╭ /// list, which is judged on the text of the path. A fetched input's spool > │ ╰──────' > 189 │ │ ╭ /// resolves a member's links inside the entry itself, and elsewhere the > │ ╰────' > 190 │ │ ╭ /// kernel resolves as the accessor would, so the walk is skipped and this > │ ╰──' > 191 │ ╭ │ /// costs the one lookup the reader needed anyway. > │ │ ╰' > 192 │ │ ╭ pub fn located( > │ ╰────────────────^ > · │ > 217 │ │ } > │ ╰───────────────' > > Error: 3 error(s) found in code. > Help: Scan succeeded and found error level diagnostics in the codebase. > For full logs, run: nix log /nix/store/5wcnsbxndhnjl9vaimixzn8gliw1mxf2-iets-ast-grep.drv error: Cannot build '/nix/store/5wcnsbxndhnjl9vaimixzn8gliw1mxf2-iets-ast-grep.drv'. Reason: builder failed with exit code 1. Output paths: /nix/store/7ghag4ad96q5nkxg0iw6xl9z33sk3pr9-iets-ast-grep