-
-
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
Uploading release files fails in v2.32.2 #2107
Comments
@egziko Interesting, my guess is that this changed behavior was introduced by some dependency version bump, since neither of the error messages exist in the Sentry CLI codebase. Can you isolate the file which is causing the upload to fail? Maybe it is indeed invalid UTF-8, and this was simply not getting checked before? |
@szokeasaurusrex |
@egziko Thanks for that information, I will try to see if I can reproduce this problem and determine why it started happening in 2.32.2. In the meantime, you can work around by using 2.32.1 |
Thank you for quickly taking care of this |
You're welcome! |
I believe this error comes from getsentry/symbolic#816 (which is already 6 months old) We should avoid putting non-js assets into the bundles, but we should obviously do that without failing the upload altogether. |
`symbolic-debuginfo` version 12.8.0 is the latest version excluding getsentry/symbolic#816, which caused a regression in `sentry-cli`. Fixes #2107
@egziko the bug should be fixed in the latest Sentry CLI release, thanks again for reporting this! |
I had it happen, then it stopped, and now it seems to be happening again. I use this in the CI script to upload:
https://github.com/p0358/black_market_edition/actions/runs/10231364720/job/28307610591
I am severely confused as to the entire reason of this change about "valid UTF-8". In principle the native apps on Windows require upload of debug symbols .PDB, accompanied with the programs themselves (.EXE, .DLL, maybe .SYS and .SCR too if I was to list it all). These programs obviously aren't UTF-8, they're binary files. And what do I see: https://github.com/getsentry/sentry-cli/blob/2a4ae9fc9a56797ddd5dee2230aa0ce344bf4277/Cargo.lock#L2811C1-L2813C19 Looks like in #2109 by @loewenheim the dep was upgraded again and the bug is thus present again... (I don't have permissions to reopen) |
@p0358, I replied on getsentry/symbolic#860. It seems to me like you might be experiencing a separate issue, and I would need some more information from you in order to be able to help |
CLI Version
2.32.2
Operating System and Architecture
Operating System Version
AlmaLinux 9.3
Link to reproduction repository
No response
CLI Command
sentry-cli releases files upload ./dist --release ${env.shortCommitId} --project ${env.SENTRY_PROJECT} --log-level=debug
Exact Reproduction Steps
After building Angular app
Works fine after downgrading to v2.32.1
Expected Results
Expected to upload release files successfully
Actual Results
Command fails with message
Logs
The text was updated successfully, but these errors were encountered: