βš‘πŸ“Š pattern filter returns empty on task output containing matches

Resolved πŸ’¬ 2 comments Opened Mar 9, 2026 by maxiboch 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 β†—