Peek & pop separately when pushing messages to BLE client#1902
Open
weebl2000 wants to merge 2 commits into
Open
Peek & pop separately when pushing messages to BLE client#1902weebl2000 wants to merge 2 commits into
weebl2000 wants to merge 2 commits into
Conversation
robekl
reviewed
Mar 3, 2026
weebl2000
force-pushed
the
no-fire-and-forget-ble-message-popping
branch
from
c520542 to
782118d
Compare
weebl2000
force-pushed
the
no-fire-and-forget-ble-message-popping
branch
from
ef73ffe to
4457394
Compare
robekl
added a commit
to robekl/MeshCore
that referenced
this pull request
Mar 23, 2026
Reimplements meshcore-dev/MeshCore PR meshcore-dev#1902 on top of 467959c for the 1.14.1 maintenance branch. References: PR: meshcore-dev#1902 Companion radio source: https://github.com/meshcore-dev/MeshCore/tree/467959cc3bfc884e5f3425caac89453a450151b6/examples/companion_radio Rationale: This patch changes the companion BLE transmit path so frames are only removed from the offline queue after the push succeeds, instead of using a fire-and-forget pop flow. The change is localized to companion radio queue handling and reduces the chance of dropping queued data when BLE delivery fails or stalls. It preserves existing interfaces and protocol behavior while making the queue semantics safer.
weebl2000
force-pushed
the
no-fire-and-forget-ble-message-popping
branch
from
4457394 to
8e3e883
Compare
I've noticed very often that the first few messages can get lost after reconnecting with BLE. This should fix that.
It shouldn't ever happen that it's less so why not
weebl2000
force-pushed
the
no-fire-and-forget-ble-message-popping
branch
from
8e3e883 to
b8edd48
Compare
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
2 participants
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.
I've noticed very often that the first few messages can get lost after reconnecting with BLE. This should fix that.
Try for yourself by building here