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

Riot duplicates calls to Scalar #5846

Closed
turt2live opened this issue Dec 17, 2017 · 3 comments · Fixed by matrix-org/matrix-react-sdk#3115
Closed

Riot duplicates calls to Scalar #5846

turt2live opened this issue Dec 17, 2017 · 3 comments · Fixed by matrix-org/matrix-react-sdk#3115
Assignees
Labels
A-Integrations P1 Privacy S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect

Comments

@turt2live
Copy link
Member

Description

Riot sends two /register requests very close together when opening Riot to a room. The first is the normal register for the manage integrations button check, however the second appears to be coming from the AppTile getting set up. Although it's not really a huge issue, it's causing uneeded duplicate data in the integration manager and homeserver (by requesting 2 sets of open ID tokens).

Version information

  • Platform: web (in-browser)
  • Browser: Chrome 63
  • OS: Windows 10
  • URL: riot.im/develop
@turt2live turt2live changed the title Riot sends two /register requests to Scalar Riot duplicates calls to Scalar Dec 18, 2017
@turt2live
Copy link
Member Author

Updated title, it's also affecting /account and probably others:

Dec-17-2017 17:14:02.366 -07:00 verbose [Webserver] Incoming request: GET /api/v1/scalar/account?scalar_token=redacted
Dec-17-2017 17:14:02.465 -07:00 verbose [Webserver] Incoming request: GET /api/v1/scalar/account?scalar_token=redacted

@lampholder lampholder added T-Defect S-Minor Impairs non-critical functionality or suitable workarounds exist P2 A-Scalar A-Widgets labels Dec 18, 2017
@turt2live
Copy link
Member Author

This seems to have gotten worse now. It makes three requests every time someone changes rooms. Luckily it's a highly cachable endpoint, but something doesn't smell good considering the number of requests it's making.

@ara4n
Copy link
Member

ara4n commented Jun 13, 2019

we shouldn't be calling /account for every room either, should we?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Integrations P1 Privacy S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants