Under particular circumstances, the NT server will send data to clients without a topic announcement. Based on my testing (using be939cb6366a5cafed1a62ce71b058525582a85d), the following seems to trigger the behavior somewhat consistently:
The client subscribes to "topics only" for a large number of topics. In my testing I used >500 topics; it doesn't seem to appear for a small number of topics.
Before a response is received from the server, the client subscribes to a topic or topics for data. The period must be short (my testing showed the issue on 0.02 but not 0.1).
The server will send a wave of topic announcements in response to the "topics only" subscription, but this will exclude topic announcements for the data subscription.
The server will start sending data for the data subscription without announcing the topics, meaning the topic IDs are unrecognized by the client.
Reversing the order of the subscriptions (data before topics only) seems to fix the issue. This also doesn't occur on the 2023 versions of NT. All of my testing has been connecting to a server running on localhost.
Under particular circumstances, the NT server will send data to clients without a topic announcement. Based on my testing (using be939cb6366a5cafed1a62ce71b058525582a85d), the following seems to trigger the behavior somewhat consistently:
Reversing the order of the subscriptions (data before topics only) seems to fix the issue. This also doesn't occur on the 2023 versions of NT. All of my testing has been connecting to a server running on localhost.