Add detailed diagnostics to issue reports - #88
Merged
Conversation
Parse the newest Nativ crash report into a readable summary (exception, termination reason, crashed-thread frames) instead of a raw excerpt, and copy the full report to the clipboard for crash reports. Inference diagnostics now include the runtime snapshot and all-time stats; the model section records the exact server launch arguments. Home-directory redaction and the URL/clipboard budget are unchanged.
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
2 participants
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.
Makes the in-app issue reporter produce reports detailed enough to triage without a round-trip.
Nativ*.ipsis present, the report now includes the exception type + signal, the termination reason (the human-readable cause, e.g. "Too many open files"), and the crashed thread's top frames, and copies the full crash report to the clipboard to paste in. Previously it only listed a short filename excerpt.No secrets are exposed: the API key and Hugging Face token live in the environment, not the launch arguments, and the whole body is still run through home-directory redaction.
This brings automated reports up to the detail of a hand-pasted crash log — like the recent file-descriptor-exhaustion report — so maintainers get the cause and backtrace up front.
looks like: