Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Account data seems broken on develop/release-1.26 #9201

Closed
turt2live opened this issue Jan 21, 2021 · 5 comments
Closed

Account data seems broken on develop/release-1.26 #9201

turt2live opened this issue Jan 21, 2021 · 5 comments
Labels
S-Major Major functionality / product severely impaired, no satisfactory workaround. T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues. X-Regression Something broke which worked on a previous release

Comments

@turt2live
Copy link
Member

Account data is not taking effect on a homeserver configured to use the main process for handling account data. There are no errors in the logs. The server is running a separate synchrotron.

The sync stream position doesn't appear to be updating, and the account data is lacking from /sync responses.
@clokep
Copy link
Contributor

clokep commented Jan 21, 2021

Just to be clear -- this is on a server including the changes in #9193?

@clokep clokep added S-Major Major functionality / product severely impaired, no satisfactory workaround. T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues. X-Regression Something broke which worked on a previous release X-Release-Blocker Must be resolved before making a release labels Jan 21, 2021
@erikjohnston
Copy link
Member

(and #9195?)

@Bubu
Copy link
Contributor

Bubu commented Jan 22, 2021

I just updated to release-v1.26.0 HEAD and that seemed to fix this problem for me.

@Bubu
Copy link
Contributor

Bubu commented Jan 22, 2021 •
edited
Loading

Well, on the other hand additional clients don't seem to get the account data updates... even after the update. 🤔

Eek, that works now as well. Maybe it needed some more time to settle.

@erikjohnston
Copy link
Member

@turt2live issue appears to be the server wasn't actually running latest develop after all.

Eek, that works now as well. Maybe it needed some more time to settle.

Yeah, it might have taken a while for all the sync streams to have caught up with all the account data it had missed.

@callahad callahad removed the X-Release-Blocker Must be resolved before making a release label Jan 28, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
S-Major Major functionality / product severely impaired, no satisfactory workaround. T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues. X-Regression Something broke which worked on a previous release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@callahad @Bubu @clokep @turt2live @erikjohnston