You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Additional context
When looking at the stats dump, all sockets are listed with the header of Socket#0. The "id" node below shows the correct socket id, though. That is maybe relevant information?
The text was updated successfully, but these errors were encountered:
gdamore
changed the title
nng_stat_find_socket on pub0 socket always returns the same stats node
nng_stat_find_socket always returns the same stats node
Apr 16, 2022
Describe the bug
I'm running
nng_stat_find_socket
on two different sockets, but the same stat node is returned for both.Expected behavior
Different sockets should have different stats, and
nng_stat_find_socket
should find the stats for the socket given.Actual Behavior
It seems like the find call just retrieves the first socket it finds, regardless of the socket passed in.
To Reproduce
This test case fails for me:
Environment Details
Additional context
When looking at the stats dump, all sockets are listed with the header of
Socket#0
. The"id"
node below shows the correct socket id, though. That is maybe relevant information?The text was updated successfully, but these errors were encountered: