Closed tsar-boomba closed 1 year ago
Upgrade to 2023.3.2. This should already be fixed there.
I updated to 2023.3.2, restarted my laptop, and updated my robot project to use 2023.3.2. However, I still have the same issue as before. Below is a screenshot of the problem and the subscription I'm using.
Do you have any other subscriptions already created before this subscription? Do all of the topics have values assigned on the server side?
This is the only subscription. The topics that I don't receive do have values, I've been working around this by restarting my client until I get the values I need.
Do you have a link to your robot project? I’m puzzled as to how this can be happening looking at the code that handles sending initial announcements and values.
This is the repo and branch I'm using https://github.com/Yeti-Robotics/aurora-java-2022/tree/development
That branch is still using 2023.1.1
Sorry, that is because I haven't pushed the change to 2023.3.2 in the build.gradle
. On my machine, it is running 2023.3.3.2
So testing your robot program in simulation, there are no values being published to several published topics:
The sim GUI NT view shows they don't have values, and no value is sent over the network.
I ran the C++ client with some WS debug-level logging turned on: https://gist.github.com/PeterJohnson/9796cab6a78438680383ebf96117fccc
I'm not sure why you're seeing a discrepancy of 16. I count 33 announced and 29 values sent in the above.
Alright, I'll look over my implementation, I must have missed something there. Thank you for your help!
Yeah, looks like a lot of values are being received before the server announces them, so I've gotta solve that now, thank you!
Huh? Values aren’t sent before they are announced (see the trace above, each announcement is followed by the value).
Yes, they are received in order, but I process messages asynchronously which is what caused the discrepancy. I'm definitely considering changing this behavior in the future, but for now, I have it worked out. Once again, thank you for your help.
Bug Description I make a NT4 subscription with an empty string
""
, prefix, and all, but the server doesn't send my subscription all the values currently recognized. All topics do get announced to the client, but only about 19 - 24 out of 36 actually have their current value sent to my client.To Reproduce Steps to reproduce the behavior:
[""]
and{"prefix": true, "all": true}
Expected behavior All currently recognized topic values are to be sent to a client that subscribes to all values when they subscribe.
Desktop:
Additional context I am using my own implementation of the NT4 spec in this repo, although this shouldn't be affecting anything because everything else works as expected.