-
-
Notifications
You must be signed in to change notification settings - Fork 227
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
npm: Useless error handling / stack traces when something breaks #2373
Comments
First of all, regarding the backtraces – these have already been fixed in Sentry CLI versions 2.40.0 and above. You should be able to see the stack traces if you upgrade to at least that version. Although, please be aware that the stack traces are primarily meant to help Sentry CLI developers; they only contain the function names in the call stack, so they likely are not that helpful for end users. The other two items you mention here do seem like real issues, however.
To keep everything organized, I am going to close this issue. We will address the problems you raised in the separate issues linked above. Please feel free to reach out if you have any further questions. |
I see, thank you for taking care of the issues distribution and I will take a look at the newer CLI version ... but I did take the latest… are you sure it got to NPM? Granted ... it get it as transitive dep of webpack plugin... |
Yeah, so the webpack plugin seems to be very much behind on the dependencies ... perhaps you can poke the other team to keep it up to date? |
Now getting this stack ... should it help something...
|
CLI Version
2.39.1
Operating System and Architecture
Operating System Version
Ubuntu 24.10
Link to reproduction repository
Not possible
CLI Command
sentry-cli upload-sourcemaps /tmp/sentry-bundler-plugin-upload-iQxDx6 --ignore node_modules --no-rewrite --use-artifact-bundle
Exact Reproduction Steps
…
Expected Results
Actual Results
I get this output (
log-level
set todebug
).url
to something that leads to a redirect… it tells me that the project was not found, not that it failed because you intentionally do not support following redirects ... leading me to spend a day hunting down wrong paths...I do get that the debug log ultimately does say that it encountered a 301/302 even though it says
project not found
or in the case of this log that thereleases
request got 502 instead ofInfo: Successfully uploaded source maps to Sentry
, but hopefully, you see that this just doesn't do what it should.Logs
The text was updated successfully, but these errors were encountered: