Skip to content

v0.6.4 - Device Timeout Parameter Fix (2025-12-26)

What Changed?

This release fixes inconsistent timeout parameter handling in example scripts. All example scripts now properly pass the timeout parameter to the device() function, ensuring consistent device initialization across the entire codebase. This is a bug fix release with no API changes.

What's New

Main Fix: Consistent Timeout Parameter Passing

What it does: Adds the missing timeout parameter to device() calls in example scripts (get_events.py, get_runs.py, get_thresholds.py). This ensures all example code follows the same device initialization pattern as the CLI and template scripts.

How to use it: No changes needed for end users. Example scripts now initialize devices consistently with proper timeout configuration.

Code example:

Before:

with device(port, mock=mock) as detector:
    cmd = Command(detector)

After:

with device(port, timeout=timeout, mock=mock) as detector:
    cmd = Command(detector)

Installation

Quick Start

# Get the release
git checkout v0.6.4

# Setup
uv sync

# Run CLI
uv run kazunoko --help

What's Different from the Last Version?

🐛 Fixed

  • Added missing timeout parameter to device() call in examples/get_events.py
  • Added missing timeout parameter to device() call in examples/get_runs.py
  • Added missing timeout parameter to device() call in examples/get_thresholds.py

Is It Safe to Upgrade?

Backward Compatible: Yes

This is a bug fix release with no breaking changes. All example scripts now follow consistent patterns without affecting the public API or CLI behavior.

Tests Passed

  • ✅ Code builds without errors
  • ✅ Pre-commit hooks pass
  • ✅ Conventional commit validation passes

Release Details

  • Date: 2025-12-26
  • Version: v0.6.4
  • Files Changed: 3
  • Commits:
  • 2a7644c: fix: add timeout parameter to device() call in get_events.py
  • f2f13f6: fix: add timeout parameter to device() call in get_runs.py
  • ee0507c: fix: add timeout parameter to device() call in get_thresholds.py
  • 133f2cc: bump: version 0.6.3 → 0.6.4

Next Steps

The next release will focus on adding new features or addressing user feedback. As always, contributions and suggestions are welcome.