Date | Commit message (Collapse) |
|
Rubyforge is dead
|
|
ref: http://spdx.org/licenses/
|
|
You may (optionally) subscribe to the new mailing list at:
clogger-public+subscribe@bogomips.org
You'll need to subscribe manually since librelist subscribers cannot be
imported. Of course, you do not have to be subscribed to post, either
(please Cc: everyone as folks may not be subscribed).
If your ISP prevents you from using port 25, port 587 (submission) is
open on bogomips.org. You may use Tor if you do not wish to expose your
IP when using port 587.
Any HTML mail will be flagged as spam, so please do not send it and
waste storage and bandwidth on it. Basic, old-fashioned mailing list
conventions apply: no top-posting, trim replies, attribute your quotes,
short signatures, etc.
This existing list will operate in public-inbox "hijack mode":
the new address is subscribed to the old librelist, so any messages
sent to the librelist are automatically archived to the new
public-inbox. Of course, not much happens here, anyways, so
nobody notices :)
Background:
Over the years, I've come to disagree with the subscription-required
posting policy of librelist. Combined with disabling of rsync archives,
one of my main reasons for choosing librelist back in the day are gone.
Lately, I've also been working on public-inbox, http://public-inbox.org/
an "archives-first" approach to mailing lists using git.
ssoma (git) archives are available at:
git://bogomips.org/clogger-public/
The ssoma format is described at http://ssoma.public-inbox.org/
HTML archives are going to http://bogomips.org/clogger-public/
All archives imported from gmane, and posts to this librelist
also go there.
|
|
|
|
wrongdoc was difficult to maintain because of the tidy-ffi
dependency and the HTML5 changes in Darkfish could not be
handled well by Tidy.
olddoc is superior as it generates leaner HTML which loads faster,
requires less scrolling and less processing power to render.
Aesthetic comparisons are subjective of course but completely
unimportant compared to speed and accessibility.
The presence of images and CSS on the old (Darkfish-based) site
probably set unreasonable expectations as to my ability and
willingness to view such things. No more, the new website is
entirely simple HTML which renders well with even the wimpiest
browser.
|
|
This is more portable across different servers than Thread.current
in case of non-blocking servers which may be serving multiple
clients at once. This is also faster than relying on $e{...} since
$e{...} uses eval and that is slow.
|
|
This updates the documentation to point to the new homepage
at http://clogger.bogomips.org/
There is one API change which removes :to_io support,
as this was never a valid Rack extension.
This also fixes a minor incompatibility which prevented the GVL from
being released on ruby-trunk (2.2.0dev) during disk operations.
The mailing list continues to be hosted at librelist, but that will
probably soon change to a public-inbox + mailing list.
There are also minor code cleanups.
This also relaxes license to LGPLv2.1 or later.
|
|
In case I'm hit by a bus, the lesser evil is to allow the FSF
to update our license than to be stuck as LGPLv3-only in the
future.
Some documentation/gemspec formatting updates while I'm at it.
|
|
StringIO isn't a very realistic use case, and our changing
the length of a shared string causes errors on 32-bit.
|
|
:to_io never was a Rack extension, and ends up breaking the case
where an SSL socket is proxied. The role of :to_io in IO-like
objects is to aid IO.select and like methods.
|
|
This updates the documentation to point to the new homepage
at http://clogger.bogomips.org/
This also fixes a minor incompatibility which prevented the GVL from
being released on ruby-trunk (2.2.0dev) during disk operations.
The mailing list continues to be hosted at librelist, but that will
probably soon change to a public-inbox + mailing list.
There are also minor code cleanups.
|
|
Rubyforge is going away on May 15, 2014.
|
|
Rubyforge about to be dead.
|
|
rb_thread_blocking_region is deprecated and will be removed
|
|
|
|
If we convert an object to string, there is a potential the
compiler may optimize away the converted string if escaping
is needed. Prevent that with RB_GC_GUARD.
|
|
RB_GC_GUARD is more explicit in intent.
|
|
We do not need it anymore
|
|
The fstat syscall should never take long, even on sockets and
slow FSes.
|
|
RAA is still dead.
|
|
RAA is dead
|
|
This release only affects users of the C extension. Users of
the pure Ruby code are not affected.
* avoid RARRAY_PTR usage for RGenGC in Ruby 2.1.0
I have not benchmarked this, but this is unlikely to be a bottleneck
at all in older Rubies. It results in a smaller binary, too, which
will help with icache bloat. This should also improve performance
under Rubinius, too.
|
|
I have not benchmarked this, but this is unlikely to be a bottleneck
at all in older Rubies. It results in a smaller binary, too, which
will help with icache bloat. This should also improve performance
under Rubinius, too.
|
|
Because we do, and this is still what I end up using all of the
time (startup performance, and I understand C, not C++)
|
|
This release enables the optional C extension on MRI Ruby 2.0.0
(and any other platform that builds C extensions).
For rare setups which do not specify a :logger or :path
parameter for Clogger#initialize, we are now Rack::Lint
compliant and call #write on env["rack.errors"] instead
of "<<"
|
|
Ruby 2.0.0preview1 is out, and we happen to be compatible
(with some harmless linker/build warnings)
|
|
1.8 did not support my preferred way of writing hashes
with symbol keys.
|
|
Rack::Lint::ErrorWrapper forbids the "<<" method. This
fallback only comes into play when no log destination
(via :logger or :path) is specified and is rarely an
issue in real setups.
|
|
It never /not/ worked under 1.9.3, but we should keep the
website up-to-date.
|
|
The use of Rack::BodyProxy#method_missing causes failures
under mainline Ruby 1.9.2 and 1.9.1, but not 1.9.3. This
test case exists to document this (now-fixed) bug for users
stuck on older Rubies.
On a side note, our usage of rb_iterate() should be rewritten
to use rb_block_call() as rb_iterate() is deprecated in 1.9.
A Ruby 1.9.2-p290 user privately reported this issue.
|
|
It's easier-to-read with the concise syntax.
|
|
|
|
This release fixes potential vulnerabilities when escape
sequences are viewed in certain terminals.
The 0x7F-0xFF byte range is escaped to match behavior of nginx
1.0.9+, as some character sets may have escape characters in
that range.
$cookie_* values are now escaped to be consistent with the
behavior of the $http_cookie value. All users of $cookie_* in
their log format must upgrade (of course there may be no
Clogger users other than myself, and I don't use $cookie_*)
|
|
These values are untrusted, so if any client sends them to us
we must escape them.
|
|
This matches the behavior of nginx 1.0.9
|
|
It's clearer that we have zero commercial intent
when using a non-profit .org domain for the mailing
list.
|
|
Nothing wrong with the GVL in Ruby 1.9.3; but we'll need
to modify our code if it's removed for C extensions.
|
|
Minor portability fixes noticed on some systems.
There is a minor license change, it is now explicitly LGPLv2.1
and LGPLv3 and later versions at the project leader's
discretion. It is no longer LGPLv2.1+, so it doesn't give a
blank check to the FSF to change the license on us.
|
|
Some Ruby installs muck up headers/#defines and cause weirdness.
We now explicitly define _BSD_SOURCE and include #stdio.h
|
|
Could be useful for some folks.
|
|
LGPLv4 could be completely different, so we won't give
the FSF a blank check to force it upon us.
|
|
* $time_iso8601 added for nginx compatibility
* $time_local (without strftime-options) is now locale-independent
There's also a minor usability tweak that allows Symbols to be
specified as the :format argument, so config.ru can be shortened:
before (continues to work with 1.0.0):
use Clogger, :format => Clogger::Format::Rack_1_0
after:
use Clogger, :format => :Rack_1_0
|
|
strftime() isn't locale-independent, so it can lead to
inconsistencies in logs.
|
|
This doesn't apply to people that use strftime()-formats,
but that's a minority.
|
|
This appeared in nginx 0.9.6
|
|
Braindamage from back in the day when I didn't understand mkmf
|
|
This allows using:
use Clogger, :format => :Rack_1_0
Instead of:
use Clogger, :format => Clogger::Format::Rack_1_0
|
|
Oops
|
|
|
|
Under 1.9, we always release the GVL for filesystem operations
now to avoid worst case scenarios. This may hurt performance
for some folks with bad locking implementations and extremely
fast filesystems. A couple of minor cleanups, too.
|