With those things considered, maybe putting them directly in the bug
tracker is a bad idea.
I am fine with putting them on the wiki if that is easiest.
The only other possibility I can think of is pushing them into a Google
calc spreadsheet, but I don't know if doing that via python is hard or
I think it would be redundant to open one issue per report when most would
just immediately be marked as duplicate, since I can see at a glance that
they're a known bug. Nicer not to have hundreds of uninteresting closed
issues. But I guess that's just being picky, plenty of projects do manage
This crash reporting feature is great. I just read through a bunch of them.
I am not sure what is best re putting the reports in the wiki. Is the idea
that we want to be able to mark them resolved? Would it be better (if
noisier) to put them in the issue tracker?
On Sun, Aug 18, 2019, 10:11 PM
I decided to added usernames to the listing and summary table because it's
the easiest way to figure out which reports are coming from the same
person, especially if they only give their email address or name once. And
the username is typically visible in a lot of log output or .rpg path
anyway.
An update.
http://tmc.castleparadox.com/ohr/reports20190819.txt
We're currently up to 52 valid crash reports, and few empty or test ones.
Here's a listing. There's better summary information now at the bottom of
the file.
There are a few interesting crashes, such as three identical ones inside in
