โšก๐Ÿ“Š pattern filter returns empty on task output containing matches

Status Closed โ€” not planned
Maintainer reply None cached
Activity 2 comments ยท opened Mar 9, 2026 ยท closed Apr 6, 2026

Bug

When using โšก๐Ÿ“Š with a pattern parameter to grep stored task output, it returns empty results even when the output definitely contains matching lines.

Reproduction

  1. Run a cargo build that produces errors: โšกโ–ถ๏ธ ['cargo check --all-features 2>&1']
  2. Build fails with 16 errors (confirmed via offset:-100 showing 'due to 16 previous errors')
  3. Try to grep: โšก๐Ÿ“Š {'action':'output','task_id':'๐Ÿ› ๏ธ33','pattern':'error\\[E','raw':true}
  4. Returns empty: {output: '', filtered: true, truncated: true}
  5. Also tried: pattern:'error', pattern:'^error' โ€” all return empty or just the summary line

Expected

Pattern filter should return all lines matching the regex from the stored output.

Workaround

Reading with negative offsets in chunks works, but defeats the purpose of the pattern filter.

View original on GitHub โ†—

This issue has 2 comments on GitHub. Read the full discussion on GitHub โ†—