iets-ast-grep
checks.x86_64-linux.ast-grep
· build #766
· raw
1bld1: building qvd1z568yzf5cahlsz9asmwdn9znlv0i-iets-ast-grep.drv2error[no-function-level-use]: move this `use` to the top of the module3 ┌─ tests/pure.rs:210:54 │ 5209 │ ╭ fn linked() -> TempDir {6210 │ │ use std::os::unix::fs::symlink;7 │ │ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^8 · │9223 │ │ }10 │ ╰─'1112error[no-comment-essays]: comment block of 8+ lines; condense it to the WHY13 ┌─ src/builtins/store_hooks.rs:191:114 │ 15184 │ ╭ /// the path resolution ended at, and its place in the (virtual) store, `None`16185 │ │ ╭ /// for one the real file system answers. [`resolve_links`] runs under a store17 │ ╰────────────'18186 │ │ ╭ /// path this evaluation copied from a local tree, and in a pure evaluation19 │ ╰──────────'20187 │ │ ╭ /// under the project: there the kernel would follow a link out of the allow21 │ ╰────────'22188 │ │ ╭ /// list, which is judged on the text of the path. A fetched input's spool23 │ ╰──────'24189 │ │ ╭ /// resolves a member's links inside the entry itself, and elsewhere the25 │ ╰────'26190 │ │ ╭ /// kernel resolves as the accessor would, so the walk is skipped and this27 │ ╰──'28191 │ ╭ │ /// costs the one lookup the reader needed anyway.29 │ │ ╰'30192 │ │ ╭ pub fn located(31 │ ╰────────────────^32 · │ 33217 │ │ }34 │ ╰───────────────'3536error[no-inline-absolute-paths]: use a `use` import instead of an inline crate::/super::/std:: path37 ┌─ src/builtins/store_hooks.rs:261:1638 │39261 │ let path = crate::compile::canon_path(path);40 │ ^^^^^^^^^^^^^^^^^^^^^^^^^^4142Error: 3 error(s) found in code.43Help: Scan succeeded and found error level diagnostics in the codebase.44