error-reporting-server
error-reporting-server copied to clipboard
phpmyadmin
phpMyAdmin server side component for the error reporting system
I get "There were no incidents reported in this time period" when looking at the all time stats, the background task is running correctly...
Sometimes it's clear from the listing of issues that these are same, so there should be a mass merge option.
We should provide reasonably big fixture with test data, so that new developers could trigger the performance issues and actually play with the server.
The stats page could include more charts to show evolution of incidents in time. - phpMyAdmin versions over time - PHP versions over time - Groupped browsers (ignoring version)
Rendering report with about 5000 incidents currently consumes about 200 MB on the server to generate. This should be reduced. Example of such report: https://reports.phpmyadmin.net/reports/view/18227
jQuery v1.8.2 https://github.com/phpmyadmin/error-reporting-server/blob/8a0a125db3841859f3f65f61f8795b02ae47d8f8/webroot/js/jquery.js latest: 3.1.0 BootStrap v2.3.2 https://github.com/phpmyadmin/error-reporting-server/blob/8a0a125db3841859f3f65f61f8795b02ae47d8f8/webroot/js/bootstrap.js latest: 3.3.7 Raphael 2.1.1 https://github.com/phpmyadmin/error-reporting-server/blob/8a0a125db3841859f3f65f61f8795b02ae47d8f8/webroot/js/raphael-min.js latest: 2.2.1 Not sure if we can upgrade them all without some code changes. Also there can...
On the stats page, the pie charts with a lot of data points can scroll outside of the area I can view. **Left side:** 
Can we provide some querying feature like https://core.trac.wordpress.org/query ? I know that we have filters on the data-table on Reports page, but I still feel this might add an extra...
There should be some persistent settings per user, for example: - Number of rows to show - Default list ordering
🎥 Server 2 always errors ("An unexpected error has occurred") after buffering
Metadata
Owner
Metadata
phpMyAdmin server side component for the error reporting system