Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

[Feature request] Persistent outbox in the companion: retry direct messages until ACKed

Ouverte
  • Quelque chose ne va pas ?
#3,519 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
c
Domaine
networking

Piste de recherche

Start by reading the related issues #3518, #1489, #1342, and #2974, plus the decision in #613, to understand the existing ACK, retransmission, and TX lifecycle behavior. Then locate the companion firmware’s message handling and companion protocol push code. Done means persistent retry and expiry behavior, deduplication, and outbox state updates work across phone disconnections and intermittent multi-hop reachability.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Goal: a DM is either delivered and ACKed, or reported as expired after a configurable retention time, also when the phone is disconnected and when the recipient is only intermittently reachable over many hops (we measured 4-hop round trips at ~32 km working intermittently, and paths of 8 to 12 hops at ~100 km).

Proposal (endpoint-only, no storage on intermediate nodes, in line with the decision in #613):

  • The companion keeps unACKed DMs in a persistent outbox in flash, instead of relying on the app to retry while connected.
  • Retry policy in the firmware: direct path first, flood with the configured scope after N failures, an immediate retry when an advert or path update from the recipient is received, and backoff otherwise (e.g. 30 s, 2 min, 10 min, 30 min, then hourly) until the retention time expires.
  • The recipient dedups on the existing message identity (timestamp + sender), so a lost ACK and a retransmission do not produce a duplicate in the app.
  • New companion-protocol push codes for outbox state changes (queued, sent, ACKed, expired), so apps can show delivery state even for messages that were ACKed while the phone was disconnected.

Why in the firmware and not the app: the radio is the always-on device and hears the recipient's adverts. App-side retries stop when the phone sleeps (notably iOS background limits) or disconnects.

Airtime: retries are mostly presence-triggered and backed off, so the flood load should stay below what users generate today by resending manually.

Depends on / related to: #3518 (ACK sent for a DM that is then dropped), #1489 (ACK reliability), #1342 (retransmission of direct messages), #2974 (TX lifecycle signalling).

Happy to discuss the design and help with smaller code changes, but I can't commit to building the full feature.

Langage dominant
C
Étoiles
3.9k
Forks
1.5k
Merge moyen
1 j 5 h
PR mergées (30 j)
24

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de meshcore-dev/MeshCore

Toutes les issues de meshcore-dev/MeshCore

Issues similaires

Plus d'issues C

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.