-
-
Notifications
You must be signed in to change notification settings - Fork 222
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
Improve debug upload output messages #1583
Comments
To clarify - .NET builds are architecture-neutral (and platform-neutral) by default. So "unknown" is the most common experience for our users. However, there are plenty of use cases where a specific platform or architecture is targeted. So if the PE/PDB has an architecture, it should still be displayed. Only omit it if it is "unknown". |
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 "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
An update on this would be appreciated. Thanks. |
Agree, especially that the message above states: "File upload complete". |
When uploading a debug information file that is architecture-neutral, Sentry CLI emits
unknown
for the architecture name. This can make it appear that there is something wrong, especially when combined with the other flags.For example, uploading files from a .NET 6 console application:
The
apphost
shows correctly that this was anarm64 executable
. But the other two are showingunknown sources
(for the source bundle) andunknown debug companion
for the symbols. This is confusing to the end-user. It would be better if the wordunknown
was simply omitted.Additionally,
PENDING
is a confusing status to report, as it seems like there's still something to be done client-side. It would be less confusing and still accurate if it saidSENT
orUPLOADED
, etc.See also getsentry/sentry-dotnet#2307
Thanks.
The text was updated successfully, but these errors were encountered: