this derivation will be built:
  /nix/store/5wcnsbxndhnjl9vaimixzn8gliw1mxf2-iets-ast-grep.drv
building '/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'
building '/nix/store/5wcnsbxndhnjl9vaimixzn8gliw1mxf2-iets-ast-grep.drv' on farm.numtide.com:50051
iets-ast-grep> elastic-arm-3e34f16b: building 5wcnsbxndhnjl9vaimixzn8gliw1mxf2-iets-ast-grep.drv
iets-ast-grep> error[no-function-level-use]: move this `use` to the top of the module
iets-ast-grep>     ┌─ tests/pure.rs:210:5
iets-ast-grep>     │  
iets-ast-grep> 209 │ ╭ fn linked() -> TempDir {
iets-ast-grep> 210 │ │     use std::os::unix::fs::symlink;
iets-ast-grep>     │ │     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
iets-ast-grep>     · │
iets-ast-grep> 223 │ │ }
iets-ast-grep>     │ ╰─'
iets-ast-grep> 
iets-ast-grep> error[no-inline-absolute-paths]: use a `use` import instead of an inline crate::/super::/std:: path
iets-ast-grep>     ┌─ src/builtins/store_hooks.rs:261:16
iets-ast-grep>     │
iets-ast-grep> 261 │     let path = crate::compile::canon_path(path);
iets-ast-grep>     │                ^^^^^^^^^^^^^^^^^^^^^^^^^^
iets-ast-grep> 
iets-ast-grep> error[no-comment-essays]: comment block of 8+ lines; condense it to the WHY
iets-ast-grep>     ┌─ src/builtins/store_hooks.rs:191:1
iets-ast-grep>     │                  
iets-ast-grep> 184 │     ╭             /// the path resolution ended at, and its place in the (virtual) store, `None`
iets-ast-grep> 185 │     │ ╭           /// for one the real file system answers. [`resolve_links`] runs under a store
iets-ast-grep>     │     ╰────────────'
iets-ast-grep> 186 │       │ ╭         /// path this evaluation copied from a local tree, and in a pure evaluation
iets-ast-grep>     │       ╰──────────'
iets-ast-grep> 187 │         │ ╭       /// under the project: there the kernel would follow a link out of the allow
iets-ast-grep>     │         ╰────────'
iets-ast-grep> 188 │           │ ╭     /// list, which is judged on the text of the path. A fetched input's spool
iets-ast-grep>     │           ╰──────'
iets-ast-grep> 189 │             │ ╭   /// resolves a member's links inside the entry itself, and elsewhere the
iets-ast-grep>     │             ╰────'
iets-ast-grep> 190 │               │ ╭ /// kernel resolves as the accessor would, so the walk is skipped and this
iets-ast-grep>     │               ╰──'
iets-ast-grep> 191 │ ╭               │ /// costs the one lookup the reader needed anyway.
iets-ast-grep>     │ │               ╰'
iets-ast-grep> 192 │ │ ╭               pub fn located(
iets-ast-grep>     │ ╰────────────────^
iets-ast-grep>     ·   │              
iets-ast-grep> 217 │   │               }
iets-ast-grep>     │   ╰───────────────'
iets-ast-grep> 
iets-ast-grep> Error: 3 error(s) found in code.
iets-ast-grep> Help: Scan succeeded and found error level diagnostics in the codebase.
iets-ast-grep> 
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