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

[stable23] Fix user status not resetting correctly after a call #31543

Merged
merged 1 commit into from
Mar 11, 2022

Conversation

backportbot-nextcloud[bot]
Copy link

backport of #31539

Only happens when the user navigated away and came back,
so the heartbeat updates the status to "Online + In a call"
After that resetting away from "Away + In a call" does not match anymore
and the previous status sticks

Signed-off-by: Joas Schilling <coding@schilljs.com>
Copy link
Member

@PVince81 PVince81 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@nickvergessen nickvergessen added 3. to review Waiting for reviews and removed 3. to review Waiting for reviews labels Mar 11, 2022
@nickvergessen
Copy link
Member

Pull request checks / Block merges during feature freezes (pull_request)

Permission to merge? @PVince81

@nickvergessen nickvergessen added the 4. to release Ready to be released and/or waiting for tests to finish label Mar 11, 2022
@PVince81
Copy link
Member

Pull request checks / Block merges during feature freezes (pull_request)

Permission to merge? @PVince81

Approved as this is a regression in RC1

@nickvergessen nickvergessen merged commit f8c7827 into stable23 Mar 11, 2022
@nickvergessen nickvergessen deleted the backport/31539/stable23 branch March 11, 2022 17:24
@blizzz blizzz mentioned this pull request Mar 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4. to release Ready to be released and/or waiting for tests to finish bug feature: status regression
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants