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.

Sign up for GitHub

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

Jump to bottom

.well-known/matrix/client should only be loaded once (not twice) on startup #2909

Open
toger5 opened this issue Dec 17, 2024 · 0 comments
Open

.well-known/matrix/client should only be loaded once (not twice) on startup #2909

toger5 opened this issue Dec 17, 2024 · 0 comments
Labels
O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Tolerable Low/no impact on users T-Defect Something isn't working: bugs, crashes, hangs, vulnerabilities, or other reported problems

Comments

@toger5
Copy link
Contributor

toger5 commented Dec 17, 2024 •
edited by hughns
Loading

TL:DR #2906 means that we might download .well-known/matrix/client twice. It should only need to do it once.

In #2906 We do a work around to fix that the client does now know about the well known content when we read from it. This has worked at some point in time so sth has changed in the startup order.

It would be great to get to the bottom of this and not do two http request for the well known but only download it once.
@toger5 toger5 added the T-Defect Something isn't working: bugs, crashes, hangs, vulnerabilities, or other reported problems label Dec 17, 2024
@robintown robintown added the S-Tolerable Low/no impact on users label Jan 7, 2025
@hughns hughns added the O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience label Jan 7, 2025
@hughns hughns changed the title Well-known loading race condition on client starup. .well-known/matrix/client should only be loaded once (not twice) on startup Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Tolerable Low/no impact on users T-Defect Something isn't working: bugs, crashes, hangs, vulnerabilities, or other reported problems
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hughns @toger5 @robintown