(the now-removed 'treat as pid' was hallunicated by the bot; the
taken-from-sentry version missed the guard against -1)
> The index of the thread that requested a dump be written in the
> threads vector. [..] If the dump was not produced as a result of an exception
> [..] this field will be set to -1,
As per the git-log, the contents of that directory were actually copied to
Bugsink from GlitchTip at GlitchTip's commit af9a700a8706, but GlitchTip itself
had copied it from Open Source Sentry, as noted in the LICENCE that they
included in their sentry directory.
(Checking Bugsink's git-log, I see that some code has since been removed from
the sentry directory, but other than that nothing substantial has been
changed).
and make the type 'Log Message'.
This may just be a matter of personal taste, but I've always found these
messages-as-type super-confusing. I'd rather have some made up (but clear,
and thanks to the whitespace unlikely-to-otherwise-exist) type "Log Message".
This is also inline in what I've already done in the UI.
This has been deprecated in Sentry in 2016; no reason for us to support it.
It is noted that despite the deprecation (in favor of `transaction`) an
explicitly provided culprit actually took a higher precedence than an
explicitly provided transaction in the now-removed code.
