You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 29, 2020. It is now read-only.
On my more busy projects the logs get filled up with
PHP Fatal error: Uncaught exception 'RuntimeException' with message 'SplFileInfo::getMTime(): stat failed for .../some/dir/filename.dat' in .../some/dir/zendframework/zend-cache/Zend/Cache/Storage/Adapter/Filesystem.php:153
The ExceptionHandler should have taken care of it actually, but somehow it doesn't anymore.
startef
Edit: Just noticed, it is not only the getMTime(). It also shows exceptions for unlink(), probably for the same reason of concurrent requests.
This issue has been moved from the
zendframework
repository as part of the bug migration program as outlined here - http://framework.zend.com/blog/2016-04-11-issue-closures.htmlOriginal Issue: https://api.github.com/repos/zendframework/zendframework/issues/7467
User: @startef
Created On: 2015-04-28T23:31:13Z
Updated At: 2015-11-06T22:14:14Z
Body
Hello,
I recently encountered an old problem that was first described and fixed here: zendframework/zendframework#6048
On my more busy projects the logs get filled up with
PHP Fatal error: Uncaught exception 'RuntimeException' with message 'SplFileInfo::getMTime(): stat failed for .../some/dir/filename.dat' in .../some/dir/zendframework/zend-cache/Zend/Cache/Storage/Adapter/Filesystem.php:153
The ExceptionHandler should have taken care of it actually, but somehow it doesn't anymore.
startef
Edit: Just noticed, it is not only the getMTime(). It also shows exceptions for unlink(), probably for the same reason of concurrent requests.
Edit2: PHP-Version is 5.5.22
Comment
User: @startef
Created On: 2015-08-17T10:20:16Z
Updated At: 2015-08-17T10:20:16Z
Body
A temporary solution was posted at heiseonline/shariff-backend-php#22
The text was updated successfully, but these errors were encountered: