drep-ai 2.7.0

A local commit gate: runs the linters your repo configures, and sends changed code to an LLM for review
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65

//! Tool resolution: criterion 24.
//!
//! The PATH lookup the deterministic runner uses when the project's own
//! copy of a tool is absent must refuse to return a `PATH` entry that
//! exists but is not executable - half-installed shims that the OS
//! would refuse to run otherwise slip through and crash a moment later
//! in `Command::spawn`, where the failure is harder to attribute.
//!
//! Both halves of the contract are pinned in one test so a resolver
//! that always returns `None` cannot pass it: the file is non-executable
//! at first (must miss), then executable (must hit, at the same path).
//!
//! `which_first` itself is private to `languages::runner`. The test goes
//! through `resolve_tool` with an empty `local_paths` list, which makes
//! the second branch the only path that can return a value - so what
//! this test pins is exactly the `which_first` behaviour the spec wants.

use std::path::Path;

use crate::languages::runner::resolve_tool_in;
use crate::languages::spec::ToolSpec;
use crate::test_support::make_executable;

/// Criterion 24: the PATH lookup rejects a non-executable PATH entry
/// and accepts the same file once the executable bit is set.
///
/// Both halves in one test. A resolver that always returns `None` would
/// fail the second assertion; a resolver that ignores the executable
/// bit would fail the first.
#[test]
fn path_lookup_skips_non_executable_then_returns_it_when_executable() {
    let dir = tempfile::tempdir().expect("tempdir");
    let tool = dir.path().join("mytool");
    std::fs::write(&tool, "#!/bin/sh\necho ok\n").expect("write tool");

    // A spec with empty `local_paths` makes the second branch the only
    // one that can return - which is the branch the criterion pins.
    let spec = ToolSpec {
        name: "mytool",
        command: &["mytool"],
        local_paths: &[],
        ..ToolSpec::default()
    };

    // The PATH value is handed in rather than written to the process
    // environment. `std::env::set_var` is `unsafe` in edition 2024 because a
    // concurrent reader is a data race, and this suite runs beside tests that
    // spawn `git` - which reads `PATH` to find it. A test-local mutex cannot
    // fix that: it excludes tests that take the same mutex, not every reader
    // in the process.
    let path = std::env::join_paths([dir.path()]).expect("a single dir joins");
    let root = Path::new("/nonexistent-root-for-test");

    assert!(
        resolve_tool_in(&spec, root, Some(path.as_os_str())).is_none(),
        "a non-executable PATH entry must be skipped"
    );

    make_executable(&tool);
    assert_eq!(
        resolve_tool_in(&spec, root, Some(path.as_os_str())).as_deref(),
        Some(tool.as_path()),
        "after chmod +x, the lookup must return the same file"
    );
}