We have deployed an early version of the error reporting server at [0]. while there are still a few things not implemented the view will not change much from what is currently there. I have filled the database with fake reports to help you see how things will look in the real world.
Since I am finishing up with the features I need feedback on the currently implemented functionality and if anyone has any idea on how to do something differently please feel free to say it.
currently there is a list of reports and clicking on the id of the report you get redirected to a view containing the summary of the related reports. you can submit error reports to the sourceforge bug tracker.
if anyone thinks there is missing functionality or if something needs to be displayed in a better way, please tell me so as to schedule the change in the coming weeks.
[0] http://reports.phpmyadmin.net/
On 08/03/2013 02:53 PM, Mohamed Ashraf wrote:
We have deployed an early version of the error reporting server at [0]. while there are still a few things not implemented the view will not change much from what is currently there. I have filled the database with fake reports to help you see how things will look in the real world.
Since I am finishing up with the features I need feedback on the currently implemented functionality and if anyone has any idea on how to do something differently please feel free to say it.
currently there is a list of reports and clicking on the id of the report you get redirected to a view containing the summary of the related reports. you can submit error reports to the sourceforge bug tracker.
if anyone thinks there is missing functionality or if something needs to be displayed in a better way, please tell me so as to schedule the change in the coming weeks.
One thing that would be good is the ability to click anywhere on a row in the list of reports to bring up the details. Right now, the link is quite small.
Bye, Rouslan
Le 2013-08-03 11:50, Rouslan Placella a écrit :
On 08/03/2013 02:53 PM, Mohamed Ashraf wrote:
We have deployed an early version of the error reporting server at [0]. while there are still a few things not implemented the view will not change much from what is currently there. I have filled the database with fake reports to help you see how things will look in the real world.
Since I am finishing up with the features I need feedback on the currently implemented functionality and if anyone has any idea on how to do something differently please feel free to say it.
currently there is a list of reports and clicking on the id of the report you get redirected to a view containing the summary of the related reports. you can submit error reports to the sourceforge bug tracker.
if anyone thinks there is missing functionality or if something needs to be displayed in a better way, please tell me so as to schedule the change in the coming weeks.
After clicking on this, then on "Login with Github", I am presented with a series of options, and only a few of them seem related to the rights I want to give.
For example, I don't see the relation between "read your followers" and the verification of my commit status.
Can it be improved?
One thing that would be good is the ability to click anywhere on a row in the list of reports to bring up the details. Right now, the link is quite small.
Bye, Rouslan
On Sat, Aug 3, 2013 at 6:38 PM, Marc Delisle marc@infomarc.info wrote:
Le 2013-08-03 11:50, Rouslan Placella a écrit :
On 08/03/2013 02:53 PM, Mohamed Ashraf wrote:
We have deployed an early version of the error reporting server at [0]. while there are still a few things not implemented the view will not change much from what is currently there. I have filled the database with fake reports to help you see how things will look in the real world.
Since I am finishing up with the features I need feedback on the currently implemented functionality and if anyone has any idea on how to do something differently please feel free to say it.
currently there is a list of reports and clicking on the id of the report you get redirected to a view containing the summary of the related reports. you can submit error reports to the sourceforge bug tracker.
if anyone thinks there is missing functionality or if something needs to be displayed in a better way, please tell me so as to schedule the change in the coming weeks.
After clicking on this, then on "Login with Github", I am presented with a series of options, and only a few of them seem related to the rights I want to give.
For example, I don't see the relation between "read your followers" and the verification of my commit status.
Can it be improved?
actually that is in github I do not control it. I request the least privileges which is basically anything you have public which anyone can get from looking at you profile. This is actually quite new. When I was working on this feature last week there was a much different view which was small and just said request access to public info. the public info includes reading of followers as well as seeing which repos are you a part of.
One thing that would be good is the ability to click anywhere on a row in the list of reports to bring up the details. Right now, the link is quite small.
Bye, Rouslan
-- Marc Delisle http://infomarc.info
Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clk... _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
From: mohamed.ashraf.213@gmail.com Date: Sat, 3 Aug 2013 20:29:53 +0200 To: phpmyadmin-devel@lists.sourceforge.net Subject: Re: [Phpmyadmin-devel] Need feedback on error reporting server
On Sat, Aug 3, 2013 at 6:38 PM, Marc Delisle marc@infomarc.info wrote:
Le 2013-08-03 11:50, Rouslan Placella a écrit :
On 08/03/2013 02:53 PM, Mohamed Ashraf wrote:
We have deployed an early version of the error reporting server at [0]. while there are still a few things not implemented the view will not change much from what is currently there. I have filled the database with fake reports to help you see how things will look in the real world.
Since I am finishing up with the features I need feedback on the currently implemented functionality and if anyone has any idea on how to do something differently please feel free to say it.
currently there is a list of reports and clicking on the id of the report you get redirected to a view containing the summary of the related reports. you can submit error reports to the sourceforge bug tracker.
if anyone thinks there is missing functionality or if something needs to be displayed in a better way, please tell me so as to schedule the change in the coming weeks.
After clicking on this, then on "Login with Github", I am presented with a series of options, and only a few of them seem related to the rights I want to give.
For example, I don't see the relation between "read your followers" and the verification of my commit status.
Can it be improved?
actually that is in github I do not control it. I request the least privileges which is basically anything you have public which anyone can get from looking at you profile. This is actually quite new. When I was working on this feature last week there was a much different view which was small and just said request access to public info. the public info includes reading of followers as well as seeing which repos are you a part of. Marc,Related links:
https://github.com/blog/1523-oauth-improvements (July 12) http://developer.github.com/v3/oauth/#scopes
- JM
One thing that would be good is the ability to click anywhere on a row in the list of reports to bring up the details. Right now, the link is quite small.
Bye, Rouslan
-- Marc Delisle http://infomarc.info
Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clk... _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
-- Mohamed Ashraf
Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clk... _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
On Sun, Aug 4, 2013 at 2:26 PM, J. M. mynetx@users.sf.net wrote:
From: mohamed.ashraf.213@gmail.com Date: Sat, 3 Aug 2013 20:29:53 +0200 To: phpmyadmin-devel@lists.sourceforge.net Subject: Re: [Phpmyadmin-devel] Need feedback on error reporting server
On Sat, Aug 3, 2013 at 6:38 PM, Marc Delisle marc@infomarc.info wrote:
Le 2013-08-03 11:50, Rouslan Placella a écrit :
On 08/03/2013 02:53 PM, Mohamed Ashraf wrote:
We have deployed an early version of the error reporting server at [0]. while there are still a few things not implemented the view will not change much from what is currently there. I have filled the database with fake reports to help you see how things will look in the real world.
Since I am finishing up with the features I need feedback on the currently implemented functionality and if anyone has any idea on how to do something differently please feel free to say it.
currently there is a list of reports and clicking on the id of the report you get redirected to a view containing the summary of the related reports. you can submit error reports to the sourceforge bug tracker.
if anyone thinks there is missing functionality or if something needs to be displayed in a better way, please tell me so as to schedule the change in the coming weeks.
After clicking on this, then on "Login with Github", I am presented with a series of options, and only a few of them seem related to the rights I want to give.
For example, I don't see the relation between "read your followers" and the verification of my commit status.
Can it be improved?
actually that is in github I do not control it. I request the least privileges which is basically anything you have public which anyone can get from looking at you profile. This is actually quite new. When I was working on this feature last week there was a much different view which was small and just said request access to public info. the public info includes reading of followers as well as seeing which repos are you a part of.
Marc, Related links:
https://github.com/blog/1523-oauth-improvements (July 12) http://developer.github.com/v3/oauth/#scopes
as I said I am using the least permissive scope possible which is none at all and that includes everything that you have public. I cannot request less than that since anything here is available while using the api even without authentication. Using no scope at all still gives you access to followed users and gists even though I donot need them that is why they appear on the permissions list. You cant deny an application something that is already public.
- JM
One thing that would be good is the ability to click anywhere on a row in the list of reports to bring up the details. Right now, the link is quite small.
Bye, Rouslan
-- Marc Delisle http://infomarc.info
Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clk... _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
-- Mohamed Ashraf
Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clk... _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clk... _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
On 08/03/2013 04:50 PM, Rouslan Placella wrote:
On 08/03/2013 02:53 PM, Mohamed Ashraf wrote:
We have deployed an early version of the error reporting server at [0]. while there are still a few things not implemented the view will not change much from what is currently there. I have filled the database with fake reports to help you see how things will look in the real world.
Since I am finishing up with the features I need feedback on the currently implemented functionality and if anyone has any idea on how to do something differently please feel free to say it.
currently there is a list of reports and clicking on the id of the report you get redirected to a view containing the summary of the related reports. you can submit error reports to the sourceforge bug tracker.
if anyone thinks there is missing functionality or if something needs to be displayed in a better way, please tell me so as to schedule the change in the coming weeks.
One thing that would be good is the ability to click anywhere on a row in the list of reports to bring up the details. Right now, the link is quite small.
Another thing that I noticed is that some urls are slipping through into the report, see attached screenshot. I think that these should be truncated to only display the filename and anything after it, but not the hostname or the path to the pma installation.
Also, I was thinking that it would be good to be able to view the full report in both json and html, for easier inspection.
Bye, Rouslan
On Sat, Aug 3, 2013 at 7:02 PM, Rouslan Placella rouslan@placella.com wrote:
On 08/03/2013 04:50 PM, Rouslan Placella wrote:
On 08/03/2013 02:53 PM, Mohamed Ashraf wrote:
We have deployed an early version of the error reporting server at [0]. while there are still a few things not implemented the view will not change much from what is currently there. I have filled the database with fake reports to help you see how things will look in the real world.
Since I am finishing up with the features I need feedback on the currently implemented functionality and if anyone has any idea on how to do something differently please feel free to say it.
currently there is a list of reports and clicking on the id of the report you get redirected to a view containing the summary of the related reports. you can submit error reports to the sourceforge bug tracker.
if anyone thinks there is missing functionality or if something needs to be displayed in a better way, please tell me so as to schedule the change in the coming weeks.
One thing that would be good is the ability to click anywhere on a row in the list of reports to bring up the details. Right now, the link is quite small.
Another thing that I noticed is that some urls are slipping through into the report, see attached screenshot. I think that these should be truncated to only display the filename and anything after it, but not the hostname or the path to the pma installation.
I am working on it. most of the urls in the stack trace has been sanitized in phpmyadmin so now the filename and query string are only displayed and they are parse so that it can detect the #PMAURL-n in the url and parse what is after it since that is the correct path.
Also, I was thinking that it would be good to be able to view the full report in both json and html, for easier inspection.
I tried it first but it messed up the formatting due to the long lines. but I can work on it to see if I can do something. what is wrong with the json view now. the reason I created it is that when I created an html view at first I found it looked worse that what you see now. I will try to think of a different way of doing things
Bye, Rouslan
Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clk... _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Hi
Dne Sat, 3 Aug 2013 15:53:24 +0200 Mohamed Ashraf mohamed.ashraf.213@gmail.com napsal(a):
We have deployed an early version of the error reporting server at [0]. while there are still a few things not implemented the view will not change much from what is currently there. I have filled the database with fake reports to help you see how things will look in the real world.
Since I am finishing up with the features I need feedback on the currently implemented functionality and if anyone has any idea on how to do something differently please feel free to say it.
currently there is a list of reports and clicking on the id of the report you get redirected to a view containing the summary of the related reports. you can submit error reports to the sourceforge bug tracker.
if anyone thinks there is missing functionality or if something needs to be displayed in a better way, please tell me so as to schedule the change in the coming weeks.
I've just pulled in latest git and I get some error. Reported it here:
https://github.com/phpmyadmin/error-reporting-server/issues
-
J. M. -
Marc Delisle -
Michal Čihař -
Mohamed Ashraf -
Rouslan Placella