midspace / midspace/SEToolbox

Improve Exception reporting

Open
#39 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

CodePlex enhancement
Dominant language
C#
Stars
156
Forks
62
PR merge metrics
No merged PRs in 30d

Description

Need to improve exception reporting.

2 considerations.

  1. At the crash dialog, allow copying of crash details, and open directly to here on GitHub to log a crash report. (Unless there is a Url query string to allow automatic pre-fill of a form.)
    See this example: https://github.com/midspace/SEToolbox/issues/new?title=Crash+Report&body=The following+details&labels=bug,question
  2. Automatic Exception reporting
    Implementing an automatic method for logging exceptions, a little like how Keen do it with Space Engineers would help considerably in collecting bug reports.

The Unhandled exception dialog should also prompt the user for whatever they were doing at the time of the Exception, and ask for any files/links they think may be important.

I'm guessing a dedicated web page, .PHP hosted somewhere that accepts a specific POST message, which will in turn email it to us.
SEToolbox can post to that specific page, with any and all detail on the error.
Some basic checks on POST fields, and on the Referer and UserAgent to prevent too much abuse or spam.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Unhandled exception dialog and tracing how crash details are currently presented. The issue does not name files or tests; define the scope for copying details, opening a prefilled GitHub report, prompting for context, and any automatic reporting endpoint before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, php
Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.