COR-1493: CLI fetches scan issues by project_name instead of scan_id,…#117
COR-1493: CLI fetches scan issues by project_name instead of scan_id,…#117Ibrahimrahhal wants to merge 1 commit into
Conversation
… causing false "Project not found" errors
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
No actionable findings found.
Verified the PR diff against main for src/inspect.rs, src/scanners/blast.rs, and src/wait.rs. The changed call chain now passes the resolved scan id into report_scan_status / fetch_and_group_scan_issues, which reaches the existing get_all_issues(..., Some(scan_id)) path and uses the pre-existing /api/v1/scan/{scan_id}/issues endpoint already exposed by list --issues --scan-id. I also checked the related command call sites, API response handling, and test tree; there are no existing API mock tests for this SAST issue aggregation path, but I did not find a concrete regression from this diff.
Validation run: RUSTUP_TOOLCHAIN=stable ./harness test passed with 211 passed. git diff --check also passed.
Sent by Cursor Automation: pr-flow
4 participants
… causing false "Project not found" errors