@llblab/pi-telegram 0.26.9 → 0.26.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/BACKLOG.md +13 -2
- package/CHANGELOG.md +4 -0
- package/package.json +1 -1
package/BACKLOG.md
CHANGED
|
@@ -2,7 +2,18 @@
|
|
|
2
2
|
|
|
3
3
|
_This backlog tracks only open release-relevant work: hotfixes, bounded maintenance, live runtime verification, evidence-gated Telegram client follow-ups, and upstream Pi API blockers. Completed outcomes and validation evidence belong in `CHANGELOG.md`, not in this queue._
|
|
4
4
|
|
|
5
|
-
## P0 — Windows
|
|
5
|
+
## P0 — Windows Graceful Disconnect Test Budget
|
|
6
|
+
|
|
7
|
+
Context: the graceful follower-disconnect integration overrides the production 30-second bus budget with 500 milliseconds even though the path persists cleanup intent, performs close/delete operations, updates binding state, and returns an authenticated response. A loaded Windows runner exceeded that artificial deadline while the same focused path completes promptly under normal scheduling.
|
|
8
|
+
|
|
9
|
+
Open work:
|
|
10
|
+
|
|
11
|
+
- [x] Give this integration-only bus round trip a realistic bounded timeout without changing production transport defaults, retries, cleanup ordering, or assertions.
|
|
12
|
+
- [ ] Validate repeatedly and across hosted platforms before publishing `0.26.10`.
|
|
13
|
+
|
|
14
|
+
Done when: slow Windows scheduling can complete the real graceful cleanup path, genuine hangs remain bounded, exact cleanup evidence stays asserted, and Linux/macOS/Windows CI passes.
|
|
15
|
+
|
|
16
|
+
## P1 — Windows Filesystem And Timer Resilience Release
|
|
6
17
|
|
|
7
18
|
Context: hosted Windows exposed two independent assumptions: atomic config replacement can transiently fail with `EPERM` while another system component holds the destination, and a five-millisecond ownership-refresh interval may not receive CPU within a 250-millisecond test deadline under runner load.
|
|
8
19
|
|
|
@@ -10,7 +21,7 @@ Open work:
|
|
|
10
21
|
|
|
11
22
|
- [x] Retry only transient Windows config-replacement errors within the existing file transaction, preserving atomic temp-file rename and bounded failure.
|
|
12
23
|
- [x] Recheck the ownership predicate at the polling boundary and give that interval regression a realistic bounded scheduling budget without changing runtime cadence or assertions.
|
|
13
|
-
- [
|
|
24
|
+
- [x] Validate focused regressions and the full suite across hosted platforms; publish and verify `0.26.9`.
|
|
14
25
|
|
|
15
26
|
Done when: concurrent config transactions survive transient destination contention, slow timer scheduling still reaches the ownership assertion, genuine failures remain bounded and diagnostic, and Linux/macOS/Windows CI passes.
|
|
16
27
|
|
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,9 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.26.10: Windows Graceful Disconnect Test Budget
|
|
4
|
+
|
|
5
|
+
- `Windows CI`: Expanded only the graceful follower-disconnect integration's bus-response budget from 500 milliseconds to five seconds. Impact: loaded Windows runners can complete persisted cleanup intent, close/delete operations, binding mutation, and the authenticated response without changing the production 30-second transport default, retry policy, cleanup ordering, or exact assertions.
|
|
6
|
+
|
|
3
7
|
## 0.26.9: Windows Filesystem And Timer Resilience
|
|
4
8
|
|
|
5
9
|
- `Config Persistence`: Retried bounded transient `EPERM`, `EACCES`, and `EBUSY` failures when atomically replacing `telegram.json` inside its existing cross-process transaction, cleaning the unique temp file on terminal failure. Impact: Windows antivirus/indexing contention no longer aborts otherwise serialized concurrent profile updates, while the live config is never deleted or rewritten non-atomically.
|