Skip to content

v0.14.0 — Open Compressed Logs and Spot Activity

Choose a tag to compare

@github-actions github-actions released this 20 Jul 09:36
· 22 commits to main since this release
6448f29

Open compressed logs directly, then use two compact visual summaries to find bursts, errors, matches, and anchors across the session.

Highlights

  • Transparent compressed-file opening supports gzip (.gz), bzip2 (.bz2), xz (.xz), and Zstandard (.zst) on static open paths: File → Open… (Ctrl+O), drag and drop, command-line file arguments, and session restore. Detection uses file content rather than the extension, and the original compressed path remains the path shown and saved in the session.
  • Decompression runs with a progress dialog and Cancel action. In a multi-file open, cancelling or failing one compressed file does not discard files already loaded and does not prevent the remaining queue from continuing.
  • View → Histogram (Ctrl+H) opens a bottom dock with time buckets stacked by detected log level. Click a bucket to jump to its first row, drag across buckets to add a time-range filter, use Z / Shift+Z or Ctrl+wheel to change bucket size, and right-click to return to automatic sizing. Anchor ticks remain visible above the chart.
  • View → Overview Rail (Ctrl+Shift+R) adds an on-by-default minimap beside the table. It summarizes the currently filtered stream, shows severity density, search-match ticks, anchor bands, and the visible viewport. Click or drag the rail to navigate. Choose Narrow, Medium, or Wide under Settings → Preferences… → Overview rail width.

Persistence and disk use

The histogram’s dock placement, size, and visibility are restored through the application’s saved window state. Overview-rail visibility and width are application preferences. Bucket counts, minimap bins, search ticks, and other derived visualization data are rebuilt from the loaded rows; they are not written into the session or exchanged through an on-disk bucket representation.

Compressed input is decoded into a temporary file in the operating system’s temp directory, then memory-mapped. The temporary file is removed when the associated log mapping is released. A default 32 GiB per-file decompressed-output limit stops decoding after output crosses that threshold. This is a fixed library default in v0.14.0, not a user preference, and it does not reserve space or check available free space in advance: decompression can still fail if the temp volume fills before the limit.

Compatibility

The session JSON schema is unchanged from v0.13.0. Existing sessions continue to load, and a compressed source saves the original compressed-file path so restore decompresses it again. Compressed files are supported only by static opening; live-tail mode and compressed log rotations remain unsupported.

The release adds bundled decompression libraries for the four codecs; their licences are included in the distributed third-party notices.

Full changelog: v0.13.0...v0.14.0