amzotall / webgrind

Automatically exported from code.google.com/p/webgrind
Other
0 stars 0 forks source link

Error handling for bad storage directory #38

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. have a storage dir (/tmp/xdebug) that doesn't exist or is not writable
2. no magic here
3. webgrind mysteriously doesn't pick up xdebug profile updates, and you
get no error message

What is the expected output? What do you see instead?
an error message telling you something is wrong

What version of the product are you using? On what operating system?
1.0, Red Hat

Please provide any additional information below.

I started a patch.  It prints an error message, nothing fancy.  How would
you recommend passing error messages to a errors.phtml?

Thanks.

Original issue reported on code.google.com by bucha...@gmail.com on 28 May 2009 at 1:48

Attachments:

GoogleCodeExporter commented 8 years ago
Good point. I'll add long overdue verification of the directories in the next 
commit.

Original comment by gugakf...@gmail.com on 8 Jul 2009 at 2:02

GoogleCodeExporter commented 8 years ago

Original comment by gugakf...@gmail.com on 28 Jul 2009 at 10:32