v0.14.6 - Add --poll-interval Option to monitor.py (2026-02-24)¶
What Changed?¶
This release adds a --poll-interval option to monitor.py that lets users configure the PollingObserver polling interval for file change detection. The default remains 1.0 second; lower values give faster updates at the cost of higher CPU usage.
What's New¶
--poll-interval Option for monitor.py¶
What it does:
Controls how frequently the PollingObserver checks monitored files for changes. Useful for tuning the trade-off between update latency and CPU load.
How to use it:
# Default: check for file changes every 1.0 second
uv run monitor.py --watch 20260224/
# Faster updates: check every 0.2 seconds (higher CPU usage)
uv run monitor.py --watch 20260224/ --poll-interval 0.2
# Slower updates: check every 5 seconds (lower CPU usage)
uv run monitor.py --watch 20260224/ --poll-interval 5.0
Key details:
- Default:
1.0second (unchanged from previous behavior) - Minimum:
0.1second - Only applies to
--watchmode; has no effect in stdin pipe mode
Installation¶
Quick Start¶
# Get the release
git checkout v0.14.6
# Setup
uv sync
# Run monitor with custom poll interval
uv run examples/monitor.py --watch /path/to/data/directory --poll-interval 0.5
What's Different from the Last Version?¶
✅ Added¶
--poll-interval FLOAToption formonitor.pyto configurePollingObserverinterval (default:1.0, minimum:0.1)
🔧 Changed¶
- Nothing changed
🐛 Fixed¶
- Nothing fixed
Is It Safe to Upgrade?¶
Backward Compatible: Yes
- Default
poll_intervalis1.0s, identical to previous hardcoded behavior monitor.pyis an example script, not a library API — no downstream code is affected
Tests Passed¶
- ✅ Builds without errors
- ✅ Commitizen conventional commits validation
- ✅
--poll-interval 0.5confirmed to detect file updates correctly
Release Details¶
- Date: 2026-02-24
- Version: v0.14.6
- Files Changed: 1 (examples/monitor.py)
- Commits: cb5e981
Next Steps¶
- Evaluate whether FSEvents can be re-enabled for non-detector file sources as an opt-in