-
-
Notifications
You must be signed in to change notification settings - Fork 225
fix: InvalidOperationException sending attachments on Android with LLVM enabled #4276
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
Conversation
…th LLVM enabled Resolves #3101: - #3101 Also see: - CA2022: https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca2022 - CA1835: https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca1835
| } | ||
|
|
||
| var read = await _innerStream.ReadAsync(buffer, offset, actualCount, cancellationToken) | ||
| // See https://github.com/getsentry/sentry-dotnet/issues/3101 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
off, some .NET bug? how can we avoid this from happening again?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't we have treat-warning-as-error on?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe we only have the Default ruleset enabled, depending on the .NET SDK version.
We could enable All rules, and also lock/pin to a specific .NET SDK ruleset for deterministic builds.
Opened new issue as follow-up for more code analysis rules and diagnostics: #4287
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't we have treat-warning-as-error on?
We do but the analyzers for this error only appear to trigger in the .NET 10 SDK (we weren't getting any errors before that).
Resolves #3101:
Also see: