-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could ConnectionInstanceNotFound in NetworkReceiverModel be reported as an ERS error? #48
Comments
Interesting...I recently changed that from an error to a log since it was occurring in places where there wasn't actually a problem...
|
At a guess, I would say that it should be a log for "connect"-type endpoints (Senders and Publishers), and an error for "bind"-type...which means additional logic should be added somewhere to distinguish those cases in NetworkReceiverModel and NetworkSenderModel (Line 137 is currently a TLOG as well)... |
In the particular scenario that I saw, the problem occurred when I tried to create a receiver with an empty string for the connection ID. Of course, it's true that this was a bug in my code, but it would have been nice for the error to be caught by the integrationtest log checking. Here is the TLOG output, in case it is of any use...
|
@eflumerf & @bieryAtFnal I'm sorry for reviving this. We see these logs in MLT and HSI application, when listening to
The logs get into tens of megabytes after just a few minutes. This can be replicated in v5 by setting all the: Network connection to This is connected to the issue here: DUNE-DAQ/trigger#354, listed by @roland-sipos. Is there an alternative way way of registering callback function/handler to network connection that might not have any receivers? |
I noticed that the error messages associated with this line were not being noticed by the log file checking in our integtests.
The reason was that the severity of the message is "LOG" based on the use of TLOG().
Could this line be changed to report an ers::error?
The text was updated successfully, but these errors were encountered: