I checked the upstream git repository and the dump_errors! method is
still the same compared to version that was reported this bug. So in
theory, the problem still persists. I also did not find any upstream bug
for this issue, did someone do that? If no, I'd kindly ask to the
affected people to do
Aliaksandr Barouski:
When error logging in sinatra fails (with exception), it can't process
exception in right way.
Example:
Our code handles Errno:EROFS:
error Errno:EROFS do
#some processing
end
If standard logger (rack.error) starts failing (e.g. filesystem become
read only), our
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Sorry for late response.
At 19 Oct 2012 18:47:45 +0300,
Eugene Lavnikevich e.lavnikev...@sam-solutions.net wrote:
Could someone please give a comment if there is any specific reason to
not incorporate the provided fix? Or maybe it's just
Hello,
this bug also affects me.
Could someone please give a comment if there is any specific reason to
not incorporate the provided fix? Or maybe it's just from the lack of
time/human resources?
Best regards
--
Eugene Lavnikevich
--
To UNSUBSCRIBE, email to
Package: ruby-sinatra
Version: 1.3.2-1
Severity: normal
Dear Maintainer,
When error logging in sinatra fails (with exception), it can't process
exception in right way.
Example:
Our code handles Errno:EROFS:
error Errno:EROFS do
#some processing
end
If standard logger (rack.error) starts
5 matches
Mail list logo
