Skip to content
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

API call users.setStatus does not trigger status update of clients #18587

Closed
stylefish opened this issue Aug 17, 2020 · 0 comments
Closed

API call users.setStatus does not trigger status update of clients #18587

stylefish opened this issue Aug 17, 2020 · 0 comments
Assignees

Comments

@stylefish
Copy link

Description:

when calling user.setStatus via API the status of the user is correctly reflected to himself but it does not update for others until the user.setStatus method is called again or the other client is reloaded.

Steps to reproduce:

  1. call REST API user.SetStatus with a status other than the current, i used the following payload to set another users status:
{
	"status": "busy",
	"message":"",
	"userId": "ABCDE"
}

the status is then update for the user user directly:
image
but not for others, for them "max" (ABCDE) is online:
image

when i change "message" in another request afterwards and keep the status the same, all clients get refreshed.
payload:

{
	"status": "busy",
	"message":"1",
	"userId": "ABCDE"
}

this behavior is reproducible every time.

Expected behavior:

When the status is changed via API the UI of others should reflect that.

Actual behavior:

The UI of others is unchanged until the client is restarted or the page is refreshed

Server Setup Information:

  • Version of Rocket.Chat Server: 3.5.2
  • Operating System: Debian 9 x64
  • Deployment Method: rocketchatctl
  • Number of Running Instances: 1
  • DB Replicaset Oplog: Enabled
  • NodeJS Version: 12.18.2
  • MongoDB Version: 4.0.19

Client Setup Information

  • Desktop App or Browser Version: Desktop App 2.17.11, current FF, Chrome
  • Operating System: Windows 10 x64

Additional context

with a change of message afterwards all clients get refreshed.

Relevant logs:

at the time of the change there are not error messages in the server log nor in the browser F12 console

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants