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

Cannot login when using wizard to configure sourcemaps due to "TypeError intermediate value is not iterable" error #3540

Open
1 task done
edgariscoding opened this issue Jan 16, 2025 · 10 comments
Assignees

Comments

@edgariscoding
Copy link
Contributor

Self-Hosted Version

25.1.0

CPU Architecture

x86_64

Docker Version

27.0.3

Docker Compose Version

2.28.1

Machine Specification

  • My system meets the minimum system requirements of Sentry

Steps to Reproduce

Using Sentry 25.1.0, run npx @sentry/wizard@latest -I sourcemaps on a local environment to configure sourcemaps.

A browser window will open and after logging in, it will display an infinite loading image along with a console error.

Expected Result

I expected for the login to succeed.

For context, we use Active Directory to log in. Everything else is working fine, I can log in successfully to access the dashboard. I only run into this issue when attempting to use the sentry wizard to configure sourcemaps.

Previously I was seeing other errors which seem to have been addressed in a recent sentry self hosted release.

Actual Result

Image

Event ID

No response

@BYK
Copy link
Member

BYK commented Jan 22, 2025

Should be resolved by getsentry/sentry#83819. Apologies for the delay! 😓

@BYK
Copy link
Member

BYK commented Jan 22, 2025

This is stemming from the same root cause of #3473.

@BYK
Copy link
Member

BYK commented Jan 22, 2025

Can you try with SENTRY_IMAGE=ghcr.io/getsentry/sentry-self-hosted:d7e6afa395e41dc314089f57ea4af33fa8bace50 and see if it works?

@getsantry getsantry bot moved this to Waiting for: Community in GitHub Issues with 👀 3 Jan 23, 2025
@JonasDev17
Copy link

Can you try with SENTRY_IMAGE=ghcr.io/getsentry/sentry-self-hosted:d7e6afa395e41dc314089f57ea4af33fa8bace50 and see if it works?

This worked for me @BYK

@getsantry getsantry bot moved this from Waiting for: Community to Waiting for: Product Owner in GitHub Issues with 👀 3 Jan 24, 2025
@BYK
Copy link
Member

BYK commented Jan 24, 2025

Yay! Are you okay running with this until the next release? Otherwise I'll try to coordinate a 25.1.1 hotfix.

@edgariscoding
Copy link
Contributor Author

Thank you for looking into this so quickly! Could you point me to the documentation to use a specific sentry image and how to reset it back to default value afterwards? I should be ok using this as well.

@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 3 Jan 24, 2025
@JonasDev17
Copy link

JonasDev17 commented Jan 24, 2025

@edgariscoding He already told you how to do it. The way I went about this is I took the SENTRY_IMAGE= part and searched for it in the code base using ctrl + shift + f (vs code). There I updated the variable to the new image. Then I looked up how to update my instance and did that - done. Fairly simple.

The SENTRY_IMAGE variable is in the .env file and to update your instance you have to run the install.sh file again - that's it.

@JonasDev17
Copy link

Yay! Are you okay running with this until the next release? Otherwise I'll try to coordinate a 25.1.1 hotfix.

All good, I am fine with that. Appreciate the help and the speedy reply!
Happy holidays!

@BYK
Copy link
Member

BYK commented Jan 24, 2025

@edgariscoding these are set by the environment variables and the defaults are stored in .env as @JonasDev17 mentioned. So you can either override it in the .env file and revert it / reset it to the latest release tag once it is out or simply add that environment variable to your environment as an override and remove it once you upgrade to the next release.

We have some docs on this buried on the main Self Hosted docs page and I think we may do a better job explaining this.

Feel free to submit a PR to the docs if you think you can make it better.

@BYK
Copy link
Member

BYK commented Jan 24, 2025

@hubertdeng123 we should close this issue once we release a new version. Should I add it to somewhere in #3530

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
Status: No status
Development

No branches or pull requests

4 participants