Skip to content
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

Unacknowledged command handling fixes and PodCommsSession improvements #45

Merged

Conversation

itsmojo
Copy link
Contributor

@itsmojo itsmojo commented Nov 18, 2024

  • Don't append an optional beep block to a getStatus with a pending unacknowledged command
  • Handle unacknowledged commands cases in acknowledgeAlerts(), beepConfig() & configureAlert()
  • Use checkCommandAgainstStatus() for seq # mismatch to determine insulin delivery status
  • Remove unneeded @discardResult attribute on various PodCommsSessions functions
  • Comment improvements and better source code synchronization between OmniKit and OmniBLE

+ Don't append an optional beep block to a getStatus with a pending unacknowledged command
+ Handle unacknowledged commands cases in acknowledgeAlerts(), beepConfig() & configureAlert()
+ Use checkCommandAgainstStatus() for seq # mismatch to determine insulin delivery status
+ Remove unneeded @discardResult attribute on various PodCommsSessions functions
+ Comment improvements and better source code synchronization between OmniKit and OmniBLE
@marionbarker
Copy link
Collaborator

Status

LGTM

Code Review

The code review looks good. Also did a comparison of OmniBLE PR 136 and OmniKit PR 45 side-by-side. The only differences between OmniBLE and OmniKit are the rileylink vs Bluetooth differences.

Refer to OmniBLE PR 136 for additional comments.

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