Bowties v0.1.5

What's New in v0.1.5

Reliability Improvements

• TCP second probe — After connecting via TCP/IP, Bowties now fires a second node probe 2 seconds after the first. This catches nodes that were slow to respond to the initial probe and would previously appear missing until the next manual refresh.

• Fixed idle timeout during config reads — The memory-read loop now grants the full timeout budget to each individual response frame rather than sharing a single shrinking wall-clock window across all frames. Large configuration reads on slow or busy networks no longer time out prematurely.

• Guard on "config read" status — A node is now only marked as fully read when zero read failures occurred. Previously, a partial read caused the node to appear fully loaded, suppressing any retry. Nodes with failed reads now stay in the failed state so the issue is visible.

Bug Fixes

• New Connection dialog too short on Ubuntu — The New Connection dialog was clipped on Linux, cutting off controls near the bottom. The dialog height is now sufficient on Ubuntu.

Diagnostics

• Copy Diagnostic Report (Tools menu) — Copies a JSON diagnostic report to the clipboard. The report includes:

  • Discovery statistics (nodes found, probe timing)
  • Per-node CDI download timing
  • Per-node configuration read statistics (batches, bytes, failed reads, total duration)
  • Event-role exchange statistics
  • A timestamped internal log (last 500 entries)

• Internal diagnostic log — Key operations (discovery, CDI download, config reads, event-role queries, TCP probe) are now logged to a 2 000-entry ring buffer, visible via the diagnostic report.