Repository navigation
Pin validated OmnipodKit backports for early-enable experiment - #1
Open
manudrijvers wants to merge 1 commit into
Open
manudrijvers wants to merge 1 commit into
manudrijvers wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pins OmnipodKit to
654f93a652535940811dc2266c9546ddd213c2d3, the exact validated handshake/key-decoding and faulted-bolus backport candidate in OmnipodKit PR #2. This makes that candidate available ontrio-o5-dex-directfor a signed Mac build. The complete Trio diff is the single OmnipodKit gitlink; application source, build configuration and the existing post-insertion control-only hook are unchanged.Merge OmnipodKit PR nightscout#2 first using a merge commit so this exact pin remains in its history. A squash or rebase requires updating and reverifying this pin before merging here.
Validation:
3e1c22f5e7e2488980966fa842d02042088057c0.Trio candidate commit:
64fd603939a45fab7cb214e94f356cbfb61ecb9e.Expected journal
runnerSourceSHA256:d74e804f70fdb386d46634b05b03ae136fc9690af31fb1f50d4c96b878908442.After merge, the remaining installation step is a signed build on the owner's Mac using the normal Trio signing process. Preserve the validated device-build settings (
-enableThreadSanitizer NO,ENABLE_THREAD_SANITIZER=NO,ENABLE_PREVIEWS=NO) and the frozen formatter'sCI=trueguard so it does not rewrite sources. The successful validation used Debug with the complete Trio scheme. Verify the source checksums before and after building and record the installed revisions.Before a physical trial, confirm that Pod Diagnostics → Pump Manager Details exposes the activation journal, the expected source stamp and build-generated Trio/Kit revisions. The experimental option remains off by default and is selected before pairing a fresh Pod; its conditional one-shot enable happens only after insertion/second-prime completion. Sensor pairing remains a separate experiment. This PR does not install an application or establish a real-Pod, delivery-safety or E2-prevention result.