Extraction of MessageQueue full via variable Bug in msg getting duplicated.
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Accessibilité débutants
- 35/100
- Type d'issue
- Bug
- Clarté
- Plutôt claire
- Activité
- À l'abandon
- Domaine
- networking, robotics
Piste de recherche
Start with ROSConnection and the outgoingQueue loop that calls OutgoingMessageSender.SendInternal, then reproduce the message drops and duplication described under Docker and Linux. Trace the Normal and QueueFullWarning states and compare the observed behavior with the reported queue-full flag workaround. Done means the queue condition and delivery behavior are understood and the issue's loss or duplication is resolved without requiring the workaround.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
Is your feature request related to a problem? Please describe.
Right now it seems that when messages are too large at some point messages get dropped however only a Debug msg ("Queue full! Messages are getting dropped!) gets displayed.
Additionally it seems that message get published then sometimes multiple times instead of just once even so the publish function was not called multiple times
This is a kinda critical bug as it will effect algorithms working with the data
Having a flag which can be check to then pause simulation/ publishing untill all message got delivered would be helpfulable.
I implemented that feature as show below.
I additionally have a subscriber on the rosside now to check that all message got delivered, then publishes a msg which gets received on unity side and only then let simulation continue,
as otherwise i always lost data at some point.
This issue seems to happen when i use it with a docker as the ros side, however under linux the issue of duplicating message also presist but i didnt observe message drops.
Describe the solution you'd like
I implement that feature in the following way i added to ROSConnection
[SerializeField]
static bool m_queuefull=false;
public bool queuefull { get => m_queuefull; set => m_queuefull = value; }
public bool Queue(){
return queuefull;
}
furthermore at the line
int count=0;
while (outgoingQueue.TryDequeue(out OutgoingMessageSender sendsOutgoingMessages))
{
OutgoingMessageSender.SendToState sendToState = sendsOutgoingMessages.SendInternal(messageSerializer, networkStream);
switch (sendToState)
{
case OutgoingMessageSender.SendToState.Normal:
//This is normal operation.
count=count+1;
//this must always be +1 one than your queue size otherwise the stuff gets stuck
//queue size should always be at least 1 larger than the amount of message you have in one go.
if(count >=4){
ROSConnection.m_queuefull=true;
}
Debug.Log("called"+count);
break;
case OutgoingMessageSender.SendToState.QueueFullWarning:
//Unable to send messages to ROS as fast as we're generating them.
//This could be caused by a TCP connection that is too slow.
Debug.LogWarning($"Queue full! Messages are getting dropped! " +
"Try check your connection speed is fast enough to handle the traffic."+count);
ROSConnection.m_queuefull=true;
break;
case OutgoingMessageSender.SendToState.NoMessageToSendError:
//This indicates
Debug.LogError(
"Logic Error! A 'SendsOutgoingMessages' was queued but did not have any messages to send.");
break;
}
token.ThrowIfCancellationRequested();
waitingSinceRealTime = s_RealTimeSinceStartup;
}
ROSConnection.m_queuefull=false;
By this we can read out if the msg queue is full in any program for example via:
ros = ROSConnection.GetOrCreateInstance();
bool rosqueuefull =ros.Queue();
Describe alternatives you've considered
Additional context
Add any other context or screenshots about the feature request here.
- Langage dominant
- C#
- Étoiles
- 2.6k
- Forks
- 473
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Préparer son environnement
- Aucun Dockerfile ni fichier Docker Compose
- Propose un modèle de pull request
- Aucun guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de Unity-Technologies/Unity-Robotics-Hub
-
Difficulté 3/5 1-2 jours Accessibilité débutants 35/100
-
ROS2,ActionOuverte
Difficulté 4/5 3-5 jours Accessibilité débutants 25/100
-
Is the project deprecated?Ouverte
Difficulté 1/5 Moins d'une heure Accessibilité débutants 20/100
-
Force/Torque sensorOuverte
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 15/100
-
Difficulté 4/5 3-5 jours Accessibilité débutants 25/100
Unity-Technologies/Unity-Robotics-Hub#433 · 1 commentaire ·
Toutes les issues de Unity-Technologies/Unity-Robotics-Hub
Issues similaires
-
DXF with empty names failsOuvertebug
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
Les mainteneurs répondent en général sous 3 jours
-
bug python
Difficulté 1/5 Moins d'une heure Accessibilité débutants 88/100
ilia-sokolov/OfficeAgent.NET#89 ·
Les mainteneurs répondent en général sous 13 jours
-
documentation
Difficulté 2/5 1-3 heures Accessibilité débutants 82/100
juandresrodca/AdminForge#66 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 70/100
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
umbraco/Umbraco.Automate#612 ·
Les mainteneurs répondent en général sous 1 jour