Closed zhutoutoutousan closed 8 months ago
Hi @zhutoutoutousan
this message appears if an Http request to sentry.io fails. You can try running
curl https://sentry.io/api/0/wizard/
and see if if you get a resonse similar to
{"hash":"<hash value>"}
Please let us know if, after trying the curl
command, you still have this problem.
This issue has gone three weeks without activity. In another week, I will close it.
But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog
or Status: In Progress
, I will leave it alone ... forever!
"A weed is but an unloved flower." โ Ella Wheeler Wilcox ๐ฅ
I also have the same problem with React Native project
Hi @iArchin can you share a reproducible example? For instance, the exact parameters with which you called the wizard? Does this happen with the latest wizard version?
Hi @Lms24.
Yes this is the latest as the Getting Started section says I just enter the npx @sentry/wizard@latest -s -i reactNative
and after the question about do I have a Sentry account I get this message:
โ Loading Wizard failed.
โ
โ Please try again in a few minutes and let us know if this issue persists: https://github.com/getsentry/sentry-wizard/issues
I tried reproducing this and for me, things load fine:
Have you tried the curl
command I posted in my initial reply?
I tried curl
but get Loading Wizard failed.
again.
Hmm Honestly, I'm not sure what's going on here. Querying the api/0/wizard/
endpoint via curl
seems to work while querying the exact same endpoint doesn't work in the wizard.
Sorry for the naive question but does this always happen or was it a one-of?
I tried
curl
but getLoading Wizard failed.
again.
I am facing this issue too
Hmm Honestly, I'm not sure what's going on here. Querying the
api/0/wizard/
endpoint viacurl
seems to work while querying the exact same endpoint doesn't work in the wizard.Sorry for the naive question but does this always happen or was it a one-of?
Always happened.
Hi @barghi and @drop0118 - we just released a new version of the wizard which will log out more details of the error/reason why this request is failing for you. Please run the wizard again (make sure to use @sentry/wizard@latest
) and paste the log output here. It's not an ideal way of debugging but I can't reproduce this at all on my end. thank you!
Hi @barghi and @drop0118 - we just released a new version of the wizard which will log out more details of the error/reason why this request is failing for you. Please run the wizard again (make sure to use
@sentry/wizard@latest
) and paste the log output here. It's not an ideal way of debugging but I can't reproduce this at all on my end. thank you!
Hey @barghi and @drop0118, I tried replacing our request library axios
with node-fetch
to see if there's a difference. Maybe Axios is adding something to the request that makes us or some party in between block the request. This is not yet released as a stable version but as a beta because I want to see if it changes anything at all. So to run this, please run
npx @sentry/wizard@3.20.3-beta.0
please let me know about the result, thanks!
@Lms24 yes the solution you mentioned fixed the issue for me thank you for that.
thanks for confirming!
@drop0118 since you were also affected - would you mind confirming the beta version fixes the issue for you too?
me too; fix this bug,please!
@St-coder I'm rarely getting annoyed by GH users but if you wanna see a bug fixed, don't just downvote me when I outline my fix ;) For instance, you could let me know if running the beta fixed the issue for you.
@St-coder I'm rarely getting annoyed by GH users but if you wanna see a bug fixed, don't just downvote me when I outline my fix ;) For instance, you could let me know if running the beta fixed the issue for you.
Sorry! I apologize for my behavior. I tried the method you provided, but it still gives an error. please help me solve it.
npx @sentry/wizard@3.20.3-beta.0
@St-coder no worries! Unfortunately, I still don't have a concrete idea what could be causing this difference in request behaviour. Given that the switch from axios
tonode-fetch
(which is what I did in the beta version) also didn't help, I don't think that it's something we do wrong in the wizard in particular. You can see for yourself, we only make a simple GET request to the very same URL: https://github.com/getsentry/sentry-wizard/blob/5a5187647fc3f755b30c5044dfa60b15abd6b8ed/src/utils/clack-utils.ts#L892
My overall suspicion for all of the errors mentioned in this thread is that an entity is interfering with the request (e.g. China's firewall). I cannot tell you how to work around this but so far all the reports we have received seem to confirm this pattern.
@St-coder no worries! Unfortunately, I still don't have a concrete idea what could be causing this difference in request behaviour. Given that the switch from
axios
tonode-fetch
(which is what I did in the beta version) also didn't help, I don't think that it's something we do wrong in the wizard in particular. You can see for yourself, we only make a simple GET request to the very same URL:My overall suspicion for all of the errors mentioned in this thread is that an entity is interfering with the request (e.g. China's firewall). I cannot tell you how to work around this but so far all the reports we have received seem to confirm this pattern.
Thank you, I have found the cause. It may be due to the Chinese firewall. After taking the steps to privatize Sentry, the issue did not occur again.
Please help me close this issue. The problem has been solved. Thank you!
Environment
Node Version: v18.14.0 Windows 11 22H2
Steps to Reproduce
turborepo
to create a package based monorepo with pnpm workspace as managernpx @sentry/wizard -i nextjs --debug
in {TURBOREPO_PATH}/app/{DESIRED_APP_PATH}/ wherepackage.json
residesExpected Result
Loading Wizard
should succeed and life should be right as rain ๐กActual Result