matrix-org / rageshake

Bug report server

matrix-org/rageshake Issues

Second line in produced log file produce non-printable characters
Updated 6 months ago
Reject reports from old version clients
Closed 9 months ago2
ability to forward a rageshake to another instance
Updated 9 months ago2
Work to ensure most clients use the same identifiers for data in the metadata of rageshakes
Updated 10 months ago
When browsing reports, the web UI appears to use Basic Auth
Closed 10 months ago5
FBM-2660-7
Closed a year ago
Customer is asking for OWASP docs around how rageshake reports are collected
Updated a year ago1
Permit gzip encoded file attachments
Closed a year ago1
Latest release did not tag the right docker images
Closed a year ago
No container tags corresponding to version releases
Closed a year ago6
Rageshake should support defining a retention period
Closed a year ago3
Migrate off BuildKite
Closed 2 years ago4
Unclear "internal server error 500" when reporting bugs
Closed 2 years ago1
"Wrong host name" when using smtp on port 587
Updated 2 years ago
Rageshake support for object storage
Updated 2 years ago4
Rageshake server should offer "download all" button for all artifacts related to a report
Closed 2 years ago2
Rageshake server does not accept "log.gz" as a valid file suffix", as used by element-android
Closed 2 years ago3
User message can cause metadata fields to get obscured
Updated 2 years ago
Rageshake server should concatenate log files of the same name pattern into a single stream
Updated 2 years ago2
New release and Docker build
Closed 4 years ago3
Small improvements for the quality of the project
Closed 5 years ago1
Data fields written in random order
Closed 5 years ago5
ability to respond to rageshakes
Updated 6 years ago