update submodules OmniXXX: prevent bogus pod suspended message #366
Conversation
This file contains 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
…olusing after comms error
marionbarker
requested review from
dnzxy,
bjornoleh,
MikePlante1,
aug0211,
AndreasStokholm,
Sjoerd-Bo3 and
t1dude
as code owners
dnzxy
approved these changes
Jul 27, 2024
aug0211
approved these changes
Jul 27, 2024
|
Merging with 2 approvals. |
mountrcg
pushed a commit
to mountrcg/Trio
that referenced
this pull request
Jul 29, 2024
…_msg update submodules OmniXXX: prevent bogus pod suspended message
Merged
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.
This fixes an intermittent error where user is incorrectly told their pod is suspended.
It has been reported several times for Loop and a Loop Report file was captured one time.
This enabled analysis that this spurious message occurs when attempting to bolus following a comms error.
This change was determined to be correct from code inspection.
Please see: Bug: Incorrect pod suspended message when bolusing after comms error