[BUG] [v0.0.7] cortex logs --paths lists all files in the logs directory, not just log files

[hindshi-goi]

Project

cortex

Description

The run_paths function lists every file in the logs directory using only a path.is_file() check with no extension filter. The main log-reading path in run() restricts files to those ending in .log or .txt, but run_paths applies no such constraint. Any non-log file present in the cache/cortex/logs directory (e.g. .json, .lock, .tmp) is shown as if it were a log file.

Error Message

Debug Logs

System Information

"system_information": "Cortex:v0.0.7, OS: Ubuntu"

Screenshots

https://github.com/gorin-ai/images/blob/main/Screenshot%20From%202026-04-10%2008-52-42.png

Steps to Reproduce

• "Place a non-log file in the logs directory: touch ~/.cache/cortex/logs/test.json",
  

• "Run: cortex logs --paths",
  

• "Observe that test.json appears in the output under 'Log Files:'"
  

Expected Behavior

Only files with .log or .txt extensions are listed, consistent with the set of files that cortex logs reads and displays.",

Actual Behavior

Every regular file in the logs directory is listed regardless of extension. Files such as .json or .lock that are not log files appear in the output as if they were logs.",

Additional Context

src/cortex-cli/src/logs_cmd.rs lines 266-286: run_paths iterates entries and pushes to log_files on path.is_file() alone, with no extension check. By contrast, run() at lines 116-122 filters with name.ends_with(\".log\") || name.ends_with(\".txt\").",

[atlas-cortex]

✅ Validation Summary — Issue #52680

All validation checks passed. 1/17 code rules failed | 1 PENALIZE | 14 LLM instructions active

Confidence Score: 4/5

• All validation checks passed. This submission meets the bounty requirements.

Validation Checks

Check	Status	Detail
Media Evidence	✅ Pass	Evidence found and accessible
Spam Detection	✅ Pass	Score: 28% — no spam signals
Duplicate Detection	✅ Pass	No significant overlap with existing issues
Code Verification	✅ Pass	Bug confirmed in source code (confidence: 100%) — The code confirms the bug. The run_paths function in logs_cmd.rs only checks
Edit History	✅ Pass	No suspicious edits
LLM Evaluation	✅ Pass	All validation checks passed. 1/17 code rules failed

Validation Pipeline

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["Issue #52680"] --> B{"Media Check"}
    B -->|"✅ Found"| C{"Spam Check"}
    C -->|"✅ Clean"| D{"Duplicate Check"}
    D -->|"✅ Unique"| CV{"Code Verify"}
    CV -->|"✅ Confirmed"| E{"Edit History"}
    E -->|"✅ Normal"| F{"LLM Evaluation"}
    F -->|"✅ Valid"| G["✅ Approved"]
    style G fill:#51cf66,color:#fff

Loading

Raw Evidence

{
  "media": {
    "hasMedia": true,
    "accessible": true,
    "urls": [
      "https://github.com/gorin-ai/images/blob/main/Screenshot%20From%202026-04-10%2008-52-42.png"
    ],
    "evidence": [
      "Found 1 media URL(s) via markdown parsing",
      "1 URL(s) accessible"
    ]
  },
  "spam": {
    "overallScore": 0.2847593582887701,
    "details": "template=0.34 (2 recent issues compared); burst=0.50 (3 issues in 2h window); parity=0.00; overall=0.28 (threshold=0.7)"
  },
  "duplicate": {
    "isDuplicate": false,
    "similarity": 0.594718124589153,
    "topSimilar": [
      {
        "issueNumber": 51691,
        "title": "[BUG] `cortex logs --clear` removes any old file in the logs directory instead of only `.log` and `.txt` log files",
        "similarity": 0.594718124589153
      },
      {
        "issueNumber": 52660,
        "title": "[BUG] [v0.0.7] `cortex logs` reads `~/.cache/cortex/logs` while `cortex debug paths` reports logs under `<cortex_home>/logs`",
        "similarity": 0.5892228707562064
      },
      {
        "issueNumber": 52640,
        "title": "[BUG][v0.0.7] `cortex logs --session` / `-s` is accepted but never filters log output",
        "similarity": 0.5820826491101159
      },
      {
        "issueNumber": 52644,
        "title": "[BUG] [v0.0.1] cortex logs --clear prints 'No old log files to clear' when logs directory is unreadable",
        "similarity": 0.5758264145283414
      },
      {
        "issueNumber": 52629,
        "title": "[BUG] [v0.0.1] cortex logs --clear silently ignores remove_file errors and exits 0\",",
        "similarity": 0.5496605316096388
      }
    ]
  },
  "editHistory": {
    "fraudScore": 0,
    "editCount": 0,
    "details": "No edits detected"
  },
  "codeVerification": {
    "plausible": true,
    "confidence": 1,
    "reasoning": "The code confirms the bug. The `run_paths` function in `logs_cmd.rs` only checks if the path is a file (`path.is_file()`) and does not filter by file extension. This means any file placed in the logs directory, such as `.json` or `.lock`, will be listed by `cortex logs --paths`.",
    "codeEvidence": "In `src/cortex-cli/src/logs_cmd.rs`, the `run_paths` function iterates over entries in the logs directory and pushes them to `log_files` if `path.is_file()` is true. It does not check if the file extension is `.log` or `.txt`, unlike the `run` function which explicitly filters by extension.",
    "screenshotValid": true,
    "screenshotReasoning": "The screenshot analysis tool returned valid=true, indicating the screenshot shows a real user-facing bug."
  },
  "rules": {
    "codeResults": {
      "passed": [
        {
          "ruleId": "content.no-profanity",
          "category": "content",
          "severity": "flag",
          "passed": true,
          "message": "Issue should not contain excessive profanity or abusive language",
          "weight": 1
        },
        {
          "ruleId": "content.reasonable-length",
          "category": "content",
          "severity": "flag",
          "passed": true,
          "message": "Issue body should not exceed 15000 characters (possible spam dump)",
          "weight": 1
        },
        {
          "ruleId": "content.has-context",
          "category": "content",
          "severity": "penalize",
          "passed": true,
          "message": "Issue should mention the affected page, component, or URL",
          "weight": 0.2
        },
        {
          "ruleId": "media.require-evidence",
          "category": "media",
          "severity": "require",
          "passed": true,
          "message": "Issue must include at least one screenshot or video URL",
          "weight": 1
        },
        {
          "ruleId": "media.must-be-accessible",
          "category": "media",
          "severity": "require",
          "passed": true,
          "message": "All media URLs must be publicly accessible (HTTP 200)",
          "weight": 1
        },
        {
          "ruleId": "media.no-placeholder-urls",
          "category": "media",
          "severity": "reject",
          "passed": true,
          "message": "Media URLs should not be placeholder or example URLs",
          "weight": 1
        },
        {
          "ruleId": "scoring.suspicious-edits",
          "category": "scoring",
          "severity": "penalize",
          "passed": true,
          "message": "Penalize issues with concerning edit history (fraud score > 0.3)",
          "weight": 0.25
        },
        {
          "ruleId": "spam.high-score-reject",
          "category": "spam",
          "severity": "reject",
          "passed": true,
          "message": "Reject issues with spam score above 0.85",
          "weight": 1
        },
        {
          "ruleId": "spam.generic-title",
          "category": "spam",
          "severity": "penalize",
          "passed": true,
          "message": "Title should not be a generic/template title",
          "weight": 0.4
        },
        {
          "ruleId": "spam.body-is-title-repeat",
          "category": "spam",
          "severity": "penalize",
          "passed": true,
          "message": "Body should not be a simple repetition of the title",
          "weight": 0.5
        },
        {
          "ruleId": "spam.no-ai-filler",
          "category": "spam",
          "severity": "flag",
          "passed": true,
          "message": "Body should not contain obvious AI-generated filler phrases",
          "weight": 1
        },
        {
          "ruleId": "validity.min-body-length",
          "category": "validity",
          "severity": "reject",
          "passed": true,
          "message": "Issue body must be at least 50 characters",
          "weight": 1
        },
        {
          "ruleId": "validity.min-title-length",
          "category": "validity",
          "severity": "reject",
          "passed": true,
          "message": "Issue title must be at least 10 characters",
          "weight": 1
        },
        {
          "ruleId": "validity.no-empty-body",
          "category": "validity",
          "severity": "reject",
          "passed": true,
          "message": "Issue body must not be empty or only whitespace",
          "weight": 1
        },
        {
          "ruleId": "validity.has-steps-or-description",
          "category": "validity",
          "severity": "penalize",
          "passed": true,
          "message": "Issue body should contain structured content (steps, expected/actual behavior)",
          "weight": 0.3
        },
        {
          "ruleId": "validity.not-a-feature-request",
          "category": "validity",
          "severity": "flag",
          "passed": true,
          "message": "Issue should describe a bug, not a feature request",
          "weight": 1
        }
      ],
      "failed": [
        {
          "ruleId": "scoring.duplicate-threshold",
          "category": "scoring",
          "severity": "penalize",
          "passed": false,
          "message": "Issue has moderate similarity to existing issues, suggesting partial overlap.",
          "weight": 0.3
        }
      ]
    },
    "llmInstructions": [
      "Always prioritize concrete evidence (screenshots, videos, URLs) over the quality of the written description. A poorly written report with clear visual proof of a bug is VALID. A beautifully written report with no evidence is INVALID.",
      "A valid bug report must contain enough information for an engineer to reproduce the issue. If the steps to reproduce are missing or impossibly vague (\"it just broke\"), the issue is INVALID.",
      "You MUST call the deliver_verdict function exactly once. Do not output a JSON object manually. Do not output your verdict in plain text. Use the tool.",
      "Be highly suspicious of submissions that follow a rigid template: same structure, same phrasing, with only the page name or URL swapped. These are template-farmed and should be INVALID. Look for: identical sentence structure, placeholder-like descriptions, formulaic \"Steps to Reproduce\".",
      "When similar issues exist, the OLDER issue (lower issue number) always takes precedence. The newer submission is the duplicate, never the other way around.",
      "Confidence scores must be calibrated: use 0.9+ only when evidence is unambiguous and complete. Use 0.5-0.7 when the issue is borderline. Use below 0.5 when you are genuinely uncertain. Never default to 0.5 — commit to a direction.",
      "Do not give the benefit of the doubt. Missing evidence means INVALID. Unclear reproduction steps means INVALID. Inaccessible media means INVALID. The burden of proof is on the submitter.",
      "In the reasoning field, explain your step-by-step analysis BEFORE stating your conclusion. Cover: evidence quality, clarity, spam signals, and duplicate overlap in that order.",
      "Never mention internal scoring thresholds, rule IDs, detection heuristics, or system architecture in the recap field. The recap is public-facing. Keep reasoning technical but recap user-friendly.",
      "If the issue body reads like AI-generated boilerplate (phrases like \"It is important to note\", \"Furthermore\", \"In conclusion\", excessive politeness, no specific technical details), treat it as strong evidence of spam. AI-generated issues with no real bug details are INVALID.",
      "If the pre-computed media check says media URLs exist, verify the description matches what a screenshot would show. If the description talks about a login page but the context suggests the screenshot is of something unrelated, flag this as suspicious.",
      "Never soften a verdict out of sympathy. \"I can see you tried hard but...\" is not acceptable. If the submission does not meet criteria, it is INVALID regardless of apparent effort.",
      "Write your reasoning and recap in a professional, neutral tone. Do not be sarcastic, condescending, or emotional. State facts.",
      "The recap field must be 2-3 sentences maximum. It will be posted as a public comment. No bullet points in recap — use flowing prose."
    ],
    "totalCodeRules": 17,
    "totalLLMRules": 14,
    "hasReject": false,
    "hasFailed": true,
    "penaltyScore": 0.3,
    "summary": "1/17 code rules failed | 1 PENALIZE | 14 LLM instructions active"
  }
}

_{Validated by Atlas • 2026-04-09}

[GreyforgeLabs]

Implemented in CortexLM/cortex-code#399

Validation run:

• cargo test -p cortex-cli --test logs_paths --no-default-features --features cortex-tui -- --nocapture
• cargo check -p cortex-cli --no-default-features --features cortex-tui
• cargo fmt --package cortex-cli --check
• git diff --check
• git diff --cached --check