pmmp / crasharchive Goto Github PK

This would be preferable to manually creating accounts on the system

This can be used to filter out noise from end-of-life versions.

When logging in, /login remains in the browser history, so clicking the back button sends you right back to the /login page. Because you're already logged in, it shows an error.

This might be a materializecss bug.

The list of crashes (as seen here) should not include crashes that were caused solely by a plugin; if someone were to go looking through the list so that they can make a pull request to fix the issue, it would make no sense to include the crashes caused by plugins on the list. The user should have an option to view the following at a time.

1. Plugin Crashes Only
2. Software Crashes Only to to
3. Plugin and Software Crashes

I plan on making a pull request implementing this change if it is accepted. What are your thoughts on this change?

Was trying to submit multiple crash dumps but all returns Error 418: I'm a teapot.
UsingChrome Version 75.0.3770.100

And here's the crash dumps:
Wed_Jul_17-09.28.59-UTC_2019.log
Wed_Jul_17-07.26.10-UTC_2019.log

This would emit JSON directly to the browser, allowing viewing of crashdump elements not rendered by the browser.

Currently there's no way to tell apart a plugin-caused crash from a core crash in /list. There's also no filters on /search that can be used for this.

A lot of server owners modify their servers for one reason or another. In a lot of cases, such users will encounter the same problems that a user with an unmodified build will have.

Instead of rejecting invalid builds, we should accept them but flag them in a nice visible colour as "modified build", and allow them to be filtered from /list.

Currently a deferred recovery is used to prevent bad crashdumps from crashing the server. However, this also allows undesired recovery from things that are actually bugs, such as a slice index out of bounds.

This should be solved by encapsulating crashdump decoding inside a dedicated function which can have a deferred recovery of its own.

Instead of the awkward "build number" comparison we have now, it would be better to be able to multi select versions that we want to see crashes from. This can be done by keeping a table of all the known versions, and then using that table to display a list of options on /search.

I get those errors
root@v1754 ~/ca-pmmp/src/github.com/pmmp/CrashArchive # make build/linux GOOS=linux go build -o ./bin/ca-pmmp-linux main.go:10:2: cannot find package "github.com/pmmp/CrashArchive/app" in any of: /usr/lib/go-1.7/src/github.com/pmmp/CrashArchive/app (from $GOROOT) ($GOPATH not set) main.go:11:2: cannot find package "github.com/pmmp/CrashArchive/app/crashreport" in any of: /usr/lib/go-1.7/src/github.com/pmmp/CrashArchive/app/crashreport (from $GOROOT) ($GOPATH not set) main.go:12:2: cannot find package "github.com/pmmp/CrashArchive/app/database" in any of: /usr/lib/go-1.7/src/github.com/pmmp/CrashArchive/app/database (from $GOROOT) ($GOPATH not set) main.go:13:2: cannot find package "github.com/pmmp/CrashArchive/app/router" in any of: /usr/lib/go-1.7/src/github.com/pmmp/CrashArchive/app/router (from $GOROOT) ($GOPATH not set) main.go:14:2: cannot find package "github.com/pmmp/CrashArchive/app/template" in any of: /usr/lib/go-1.7/src/github.com/pmmp/CrashArchive/app/template (from $GOROOT) ($GOPATH not set) main.go:15:2: cannot find package "github.com/pmmp/CrashArchive/app/webhook" in any of: /usr/lib/go-1.7/src/github.com/pmmp/CrashArchive/app/webhook (from $GOROOT) ($GOPATH not set) Makefile:10: recipe for target 'build/linux' failed make: *** [build/linux] Error 1

• lastError
• parameters
• extensions
• phpinfo

These fields are sent by PocketMine-MP but not read by the crash archive.

A randomly-generated token can be provided to the issue submitter, which must be provided to delete the crashdump.

It would be great to find crash by plugin with its version, or at least somehow show plugin versions on the crash list. For example, when I am looking for crashes in my plugins, most of those are already patched in newer versions. Adding this feature would solve the problem.

This could be interesting as a "hall of fame" page.