-
|
Hi guys, i am starting to receive some weird logs when two instances are alive at the same time on the same machine, one as sender and one as receiver . For the life of me i cannot understand where these logs are coming from, and they're just polluting my console :))) UPDATED RECV rate: 64.040602 kbps nsize: 1243.948537 |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 1 reply
-
|
Nevermind, i found the culprit: there were some TRACE() messages in normNode.cpp . |
Beta Was this translation helpful? Give feedback.
-
|
It's a TRACE line -- if you turn trace off, it should not appear. |
Beta Was this translation helpful? Give feedback.
-
|
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
@font-face
{font-family:"Times New Roman \(Body CS\)";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
-->Hi, I suspect this is an artifact from some recent debugging code that I overlooked eliminating before pushing some updates to the repo … This one is from a “TRACE” state in “src/common/normNode.cpp” (and there are others). I usually scrub TRACE() statements before any commits to Github and didn’t do that at some point here (apologies!). I work to remedy this as quickly as possible. Best regards, Brian From: luc1an ***@***.***>Date: Monday, March 31, 2025 at 8:01 AMTo: USNavalResearchLaboratory/norm ***@***.***>Cc: Subscribed ***@***.***>Subject: [USNavalResearchLaboratory/norm] Weird logs (Discussion #94)Hi guys, i am starting to receive some weird logs when two instances are alive at the same time on the same machine, one as sender and one as receiver . For the life of me i cannot understand where these logs are coming from, and they're just polluting my console :)))See below a sample. The rates>1kbps are logged when there's an incoming object, and the ones<1kbps are when the receiver is idle, just waiting for something new to come up.This is happening even when i am setting the NormInstance debug level is 0.UPDATED RECV rate: 64.040602 kbps nsize: 1243.948537UPDATED RECV rate: 63.930980 kbps nsize: 1243.948537UPDATED RECV rate: 42.292990 kbps nsize: 1183.151110UPDATED RECV rate: 63.930980 kbps nsize: 1183.151110UPDATED RECV rate: 42.292990 kbps nsize: 1125.393554UPDATED RECV rate: 63.930980 kbps nsize: 1125.393554UPDATED RECV rate: 0.224091 kbps nsize: 1070.523877UPDATED RECV rate: 4.197301 kbps nsize: 1070.523877UPDATED RECV rate: 0.471842 kbps nsize: 1018.397683UPDATED RECV rate: 4.197301 kbps nsize: 1018.397683UPDATED RECV rate: 0.471842 kbps nsize: 968.877799UPDATED RECV rate: 4.197301 kbps nsize: 968.877799UPDATED RECV rate: 0.471842 kbps nsize: 921.833909UPDATED RECV rate: 4.197301 kbps nsize: 921.833909—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
@font-face
{font-family:"Times New Roman \(Body CS\)";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
-->Unfortunately, “trace off” in the NORM code is only with respect to per-packet send/receive logging and doesn’t control TRACE() calls. I need to scrub those from the github commit that mistakenly included them. Cheers, Brian From: Jeff Weston ***@***.***>Date: Monday, March 31, 2025 at 8:51 AMTo: USNavalResearchLaboratory/norm ***@***.***>Cc: Subscribed ***@***.***>Subject: Re: [USNavalResearchLaboratory/norm] Weird logs (Discussion #94)It's a TRACE line -- if you turn trace off, it should not appear.—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Oh you're right -- I'll remove those real quick. |
Beta Was this translation helpful? Give feedback.
-
|
Relevant TRACE debugging lines from bc6e81f commented out in 1c534c0 |
Beta Was this translation helpful? Give feedback.
Nevermind, i found the culprit: there were some TRACE() messages in normNode.cpp .
I commented those and now it's ok :)