Skip to content

Logic fix for 049 pod fault with concurrent temp basal commands #48

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 18, 2025

Conversation

itsmojo
Copy link
Contributor

@itsmojo itsmojo commented Jan 18, 2025

  • Fixes Trio issue #455, see for more details
  • Tweaks to runTemporaryBasalProgram() to avoid using stale podState
  • Change enactBolus() to use same updated pod suspended testing logic

+ Fixes Trio issue #455, see for more details
+ Tweaks to runTemporaryBasalProgram() to avoid using stale podState
+ Change enactBolus() to use same updated pod suspended testing logic
Copy link
Collaborator

@marionbarker marionbarker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Status

This update is accepted by code review.

Code Review

  • The 0x31 fix in the runTemporaryBasalProgram function comes from replacing the stale podState (from line 1952) before the lock (at runSession) with the podState obtained inside the lock (line 1992) which can be used for subsequent podState checks
  • The modification to the enactBolus function was not required but is good form to match the syntax of the runTemporaryBasalProgram function

The code changes from this PR and OmniBLE PR140 are identical.

Sign up for free to 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.

2 participants