Is the dev branch ready for a release? We're running it production and
at least three times a week it starts spinning and writing this to the
logs in an endless loop:
Fri, 22 Jun 2012 16:04:50 GMT [ERROR] (src/task/fd.c:217: errno: None)
Attempt to wait on a dead socket/fd: (nil) or -1
The server fills up a 500G disk in about 11 hours and we need to kill
the server to get it handling requests again.
Additionally there is a bug with handlers that prevents them from
getting called on the CLOSE state. I've submitted a pull request (#132
<https://github.com/zedshaw/mongrel2/pull/132>) for it but haven't
gotten any feedback on it.
I've also put in a pull request for a change to the filters api that is
not backwards compatible. It seems like getting that into the 1.8
release (along with the first "release" of filters) would be an easy
thing to make as opposed to changing it later (if it's accepted)
-Rob
On 6/18/12 2:10 AM, Loic d'Anterroches wrote:
Hello,
short question. What is preventing a 1.8 release of Mongrel2? Do you
think we can set a date to do a release this summer?
This way we can start to work on the many things people need which could
affect the backward compatibility like HTTPS header or
TRUSTED_HEADER_FOO etc.
loïc
