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

SvelteKit wizard returns TimeoutError #555

Open
michaelchai-sentry opened this issue Mar 29, 2024 · 2 comments
Open

SvelteKit wizard returns TimeoutError #555

michaelchai-sentry opened this issue Mar 29, 2024 · 2 comments

Comments

@michaelchai-sentry
Copy link

Environment

One of our customers reported that they get a TimeoutError when they try to use the SvelteKit wizard to set up a new project

Steps to Reproduce

  1. Use SvelteKit wizard
  2. Select that you already have a Sentry account
  3. Try to log into sentry.io with the link provided by the wizard

Expected Result

Continue the setup through the wizard

Actual Result

Get the Server Error page (screenshot)
Screenshot 2024-03-29 at 2 40 49 PM

@Lms24
Copy link
Member

Lms24 commented Apr 2, 2024

Hey @michaelchai-sentry I just tried running the SvelteKit wizard. Once with already being logged in before starting the wizard and once with logging in within the wizard flow. In both cases, I couldn't reproduce this error. Do you have any more insights into the customer's network setup? Usually, we get errors in this step when users have network issues or block certain requests. However in this case, it looks like there might be an error within the Sentry application. Any chance this happened during an incident?

@AbhiPrasad
Copy link
Member

@Lms24 this is the following sentry error: https://sentry.sentry.io/auth/login/sentry/?next=%2Fissues%2F4974702451%2Fevents%2Faa4c48000beb432a8741b56d0652c807%2F%3Fproject%3D1

From slack: https://sentry.slack.com/archives/C05LTSKSG6T/p1711477829219289

The wizard pulls all projects and for a big org like REMOVED it takes too much time to read all the rows and turn them into a response. The solution for sdk-wizard would be to limit the results we fetch. We had that in place before but sdk-wizard folks asked that those limits be removed. Putting the limits back could be a path forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

3 participants