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

last_active_ago is updated on sync when it shouldn't be #12424

Open
matrixbot opened this issue Dec 19, 2023 · 0 comments
Open

last_active_ago is updated on sync when it shouldn't be #12424

matrixbot opened this issue Dec 19, 2023 · 0 comments

Comments

@matrixbot
Copy link
Collaborator

matrixbot commented Dec 19, 2023

This issue has been migrated from #12424.


Description

The last_active_ts is updated for a user when they perform a regular sync request where their previous presence is 'online'. It looks like synapse intends to only update this when a sync is performed with set_presence = online and the previous presence state is online, and the spec says it should only be updated on a proactive event from the user.

This is because set_state is called in order to set the new presence state and this method always updated last_active_ago.

Found while working on matrix-org/synapse#12213 but I think this will need another inter-process API added to fix.

Steps to reproduce

  • Have two users, leave one syncing.
  • On the other user, perform a sync request
  • Notice on the first sync stream that the last_active_ago value for the other user reflects the the sync you just did.

Version information

  • Homeserver:

If not matrix.org:

  • Version:

  • Install method:

  • Platform:
@matrixbot matrixbot changed the title Dummy issue last_active_ago is updated on sync when it shouldn't be Dec 21, 2023
@matrixbot matrixbot reopened this Dec 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant