Skip to content

update - #6

Closed
lolos2go wants to merge 7 commits into
LoopKit:devfrom
lolos2go:dev
Closed

update#6
lolos2go wants to merge 7 commits into
LoopKit:devfrom
lolos2go:dev

Conversation

@lolos2go

Copy link
Copy Markdown

No description provided.

ddaniels1 pushed a commit to ddaniels1/LoopWorkspace that referenced this pull request May 23, 2020
* Bolus progress and quick cancellation
* Add MKRingProgressView files directly
* Update LICENCE file to include license for MKRingProgressView
* Use MKRingProgressView via carthage
* Use pumpmanager's bolusProgressEstimator
* Updates from code review:
- Delay removal of bolus progress so user sees progress finish
- Reset ring progress during cell re-use
- Tweak cornerRadius
- Code clarity updates
* PumpManager Protocol updates
* Protocol naming update
* Create bolus progress reporter
* Fix progress animating from 1 to 0 on reuse.
threecee pushed a commit to threecee/LoopWorkspace that referenced this pull request May 2, 2026
Picks up:
- OmniBLE (b4-start..5fb011a, 4 commits): payload validity 60s → 600s
+ doc comment (LoopKit#6); PhoneWatchSettingsSync v2 with automaticDosing
fields + protocol version bump (LoopKit#3); shared HandoffState.currentOwner
extension for policy-engine wiring (LoopKit#2).
- Loop (b4-start..b5e94f7a, 4 commits): iOS LoopAppManager wires
settingsSyncProvider closure (closes production gap discovered
during planning) + watch WatchSettingsSnapshot reads dosing flags
from sync (LoopKit#3); HandoffOrchestrator wires HandoffPolicyEngine
markX hooks on both sides via Combine reachability subscription
with 60s debounce (LoopKit#2); review-fix renames + safety comment.
After this, the watch can self-drive when the phone reports
automaticDosingEnabled, the auto-revert path is live (was dead code
since B.3.a), and the cached-pod-state safety gate is active.
BEHAVIOR CHANGE: auto-revert from watch back to phone WILL FIRE in
.automatic and .manualWithAutoRevert modes when the phone reconnects
after being out of range for >=60s. Worth deliberate hardware testing
on the next install.
Verified:
- OmniBLETests targeted (3 suites): 26/26 PASS
- LoopTests targeted (3 suites): 27/27 PASS
- WatchApp ExtensionTests targeted (2 suites): 19/19 PASS
- Release archive: ARCHIVE SUCCEEDED (iOS, generic destination)
threecee-claude
threecee pushed a commit to threecee/LoopWorkspace that referenced this pull request May 4, 2026
Loop: slice-tag comment prefix strip across WatchHandoff stack, WatchApp
Extension, and WatchAlgorithmKit (~57 line-comment prefixes; doc comments
preserved). HandoffPolicyEngine tick 1Hz to 5s (efficiency #1, lockstep
across iOS+watch pair). ExtendedRuntimeCoordinator gated on
HandoffOrchestrator.handoffState == .watchDriver via Combine subscription
(efficiency LoopKit#6); 3 new gating tests + 3 existing tests updated.
OmniBLE: slice-tag comment prefix strip in Common/ (state machine,
state persistence, handoff payload, ownership coordinator). No
HandoffPolicyEngine copy on OmniBLE side.
algorithm-fidelity-audit NOT required (no algorithm-adjacent files
touched). LoopTests: 303 pass, 1 skipped. WatchApp ExtensionTests: 124
pass. Tagged b9-complete on all three repos. Build 878 prep.
threecee-claude
ps2 added a commit that referenced this pull request Aug 1, 2026
… wording (#6)
Expired Libre 3 sensors now show 'Expired' (not 'Sensor failed'), surface a
prominent Pair New Sensor button, and the expiry alerts set the warmup-gap
expectation instead of implying a gap can be avoided by replacing early.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@lolos2go