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
I don't know if it's the "domain server" or the "metaverse server" that has the bug, but a user that is not connected to an account is counted 2 time in the number of user on a domain/place.
To reproduce:
As a NON-connected user, go in a domain where you know that you will be alone. The place API will return 2 as number of user in the Place and the Domain.
Wait 5 minutes
As a connected user, go in a domain where you know that you will be alone. The place API will return 1 as number of user in the Place and the Domain.
The text was updated successfully, but these errors were encountered:
This is an Iamus bug. Testing found that Iamus's interpretation of what the domain-server sends is wrong. The heartbeat sends "num_users" and "num_anon_users" and, if there is one anon user, those are both returned at "1". That is, "num_users" seems to be the total number of users and "num_anon_users" is the number of those users that are anonymous. Iamus mis-interpreted it as "num_users" being the number of logged in users.
Problem was that Iamus interpreted the domain-server "num_users" and
"anon_users" as two separate sets when, actually, the domain-server
heartbeats "num_users" as the total number of users and "anon_users"
is the number, of that total, that are anonymous.
Fixesvircadia#98
I don't know if it's the "domain server" or the "metaverse server" that has the bug, but a user that is not connected to an account is counted 2 time in the number of user on a domain/place.
To reproduce:
As a NON-connected user, go in a domain where you know that you will be alone. The place API will return 2 as number of user in the Place and the Domain.
Wait 5 minutes
As a connected user, go in a domain where you know that you will be alone. The place API will return 1 as number of user in the Place and the Domain.
The text was updated successfully, but these errors were encountered: