Repository navigation
Explain issue report submission failures clearly - #6
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replace the issue-submission failure's vague wording with a clear translated status and retry instruction. Keep report collection, asynchronous submission, metadata and success confirmation unchanged; retain the exception in the log without the humorous suffix.
Uses the shared CI and controlled-test infrastructure already integrated into master. Adds three focused tests covering send failure, success and cancellation; PR CI runs tests and package build. Tests drive the real generator with controlled boundaries and do not claim real wx scheduling or server delivery.