lighty's life: Bug fixing marathon

Bug fixing marathon

jan — Sat, 18 Aug 2007 12:02:00 +0000

Looking at the bug-system a few days ago we had something like 460 bugs open.

Quite a bunch of them were duplicates of the same issue and others were already fixed in the code and just not closed in the bug-system.

Scanning through the bugs I wrote some more test-cases to verify that the reports were valid and along the way at least these bugs got fixed:

  * added dir-listing.set-footer in mod_dirlisting (#1277)
  * fixed hardcoded font-sizes in mod_dirlisting (#1267)
  * fixed different ETag length on 32/64 platforms (#1279)
  * fixed compression of files < 128 bytes by disabling compression (#1241)
  * fixed mysql server reconnects (#518)
  * fixed disabled keep-alive for dynamic content with HTTP/1.0 (#1166)
  * fixed crash on mixed EOL sequences in mod_cgi
  * fixed key compare (#1287)
  * fixed invalid char in header values (#1286)
  * fixed invalid "304 Not Modified" on broken timestamps
  * fixed endless loop on shrinked files with sendfile() on BSD (#1289)
  * fixed counter overrun in ?auto in mod_status (#909)
  * fixed too aggresive caching of nested conditionals (#41)
  * fixed possible overflow in unix-socket path checks on BSD (#713)
  * fixed extra Content-Length header on 1xx, 204 and 304 (#1002)
  * fixed handling of duplicate If-Modified-Since to return 304
  * fixed extracting status code from NPH scripts (#1125)
  * removed config-check if passwd files exist (#1188)

Now the bug-count is at 413, a start.

"Bug fixing marathon" by HenrikH

Thu, 30 Aug 2007 07:17:22 +0000

Ok, anything special one has to do in order to mark the tickets when they contain pathes in order to seperate them from normal bug reports? #1317 and #1324 are showstoppers if you run a webdav server, yet 1.4.17 just came out without these pathes. Or am I too greedy since they have only been in trac for one week :-) ?

"Bug fixing marathon" by darix

Wed, 29 Aug 2007 09:24:57 +0000

tickets are the way to go

"Bug fixing marathon" by HenrikH

Sun, 26 Aug 2007 18:39:57 +0000

Btw, how do we send in our patches? I have two patches that I have added as tickets, is this the correct behaviour or should I sent them to some specific mail-address instead?

"Bug fixing marathon" by smiley

Thu, 23 Aug 2007 08:37:15 +0000

I would like to say a big thanks to Weigon, Darix and Moo (and anyone else i missed out on) for all the bug fixes

for a month there lighttpd looked like it was a dead project

but now commits are comming in fast and furious

@otto ive been downloading v1.5 svn releases every day and so far they are highly stable, the only problem i had (http://trac.lighttpd.net/trac/ticket/1300) was fixed very quickly by poping in and discussing the issue on IRC

"Bug fixing marathon" by darix

Tue, 21 Aug 2007 16:19:01 +0000

Frank: depends on where it uses the config. if it is mod_proxy/mod_*cgi - related, it is not fixed i think.

"Bug fixing marathon" by otto

Mon, 20 Aug 2007 11:42:18 +0000

or a new 1.5 preview release? :)

"Bug fixing marathon" by s0enke

Mon, 20 Aug 2007 10:33:50 +0000

great work. Is there a timeline for 1.4.18 minor release? Thanks!

"Bug fixing marathon" by Frank

Mon, 20 Aug 2007 04:10:58 +0000

Has the bug about Lighty eating RAM been fixed?

"Bug fixing marathon" by Jan Kneschke

Sun, 19 Aug 2007 09:46:48 +0000

Patches are welcome.

"Bug fixing marathon" by Tim

Sat, 18 Aug 2007 23:17:32 +0000

I would absolutely love to see *all* bugs fixed before the next release. That would be AWESOME!

"Bug fixing marathon" by moo

Sat, 18 Aug 2007 15:13:31 +0000

great job, jan i too scanned it twice some time ago but didn't kill much tickets as i'm not familar with most of the modules