Date | Commit message (Collapse) |
|
Fix build for platforms lacking both TCP_CORK _and_ TCP_NOPUSH
There are many test case fixes and cleanups, too.
|
|
Followup-to: e26358413c9d87e1ce8f6cda5cf0b8dd53979ed2
|
|
Under load, TCP sockets may not register as readable right away
after the writer finishes. This can be expected for
implementations where loopback TCP is a closer simulation of
non-local TCP traffic.
These test failures were noticed under FreeBSD 9.0.
|
|
We can't actually test for EPERM without changing
permissions/ownership, and we can't do that without root...
|
|
IO#readpartial may not drain the socket buffers enough for
kgio_write to succeed on some platforms. So use IO#read for
read-in-full behavior.
|
|
It makes test failures hard to track down, tests will
already fail if exceptions are thrown and we'll get
nice backtraces.
|
|
We don't need to care for TCP_NOPUSH in read_write.c, it's
entirely in autopush.c and no-op on platforms without
TCP_CORK/TCP_NOPUSH. TCP_CORK/TCP_NOPUSH are non-POSIX, so
it's entirely possible some Free systems will lack them.
Reported-by: Edho Arief <edho@myconan.net>
|
|
Fixed build and autopush support under Debian GNU/kFreeBSD.
Test case fixes for timing-sensitive tests.
|
|
Unlike most Rubyists, I prefer GNU make to Rake.
|
|
poll(2) may return successfully before it gets interrupted
by the signal.
Found and fix confirmed by 375gnu on the kgio mailing list.
ref: <CAAB-Kcm=_CRa4UoSQt+C4cHk6z2Rpfsv6_KXPHV3R34Gt6sLiQ@mail.gmail.com>
|
|
This appears to be needed for Debian GNU/kFreeBSD under KVM.
|
|
It seems autopush support in our autopush code has
always been broken outside of Linux-based systems,
as we never marked the socket as having pending data.
|
|
The check for the accept4() function actually succeeds on a
stock installation of Debian GNU/kFreeBSD 6.0, but the
eglibc headers fail to define the necessary flags.
|
|
Fix a missing #include for Ruby 1.8.5 users. No need to
upgrade to this (nor 2.7.1) if you're on a modern version
of Ruby.
|
|
Apparently the old Ruby 1.8.6 installation lying around isn't
old enough.
|
|
This release fixes some compatibility issues with people
stuck on older versions of Ruby/RubyGems.
* define RARRAY_PTR/RARRAY_LEN macros for Ruby 1.8.6
* test/test_autopush: skip strace tests if not available
* gemspec: disable development dependencies for old systems
|
|
"Enterprise" users are sometimes stuck on older Rubies/RubyGems
and this is still required for them.
|
|
No need to completely fail on a test.
|
|
Apparently Ruby 1.8.6 is still in use...
|
|
When running under Ruby trunk/2.0.0dev, all IO objects created
by kgio will be close-on-exec by default to match the (future)
2.0.0 behavior. accept()ed sockets in kgio have always been
close-on-exec by default..
Singleton Kgio.accept_* methods are deprecated as the
kgio_accept/kgio_tryaccept methods all take an additional
flags argument.
There are various, test, documentation, and error message
improvements.
|
|
There's no reason for SOCK_NONBLOCK with Ruby, and SOCK_CLOEXEC
has always been on-by-default with accept() wrappers.
|
|
All IO objects created by Kgio will have FD_CLOEXEC descriptor
flag set on it when run under Ruby 2.0.0dev. This matches the
upcoming behavior of Ruby 2.0.0dev for IO objects in the core
and standard library. This change does not affect users on Ruby
1.9.3 and earlier.
accept()-ed sockets in kgio have _always_ had FD_CLOEXEC
set by default.
|
|
There's no point in testing a Ruby implementation detail and
these tests fail under OpenBSD where the accept()-ed socket
inherits the O_NONBLOCK flag from the parent.
|
|
The kgio_accept and kgio_tryaccept methods now take an
additional flags argument, so there's no reason to set
global flags anywhere.
|
|
This is mostly an implementation detail, but it's already
true on OpenBSD (and maybe other BSDs), and also requires
no additional syscalls on newer Linux systems.
|
|
This needs to work similarly to IO.select.
|
|
We want feedback!
|
|
eye kan spel!
|
|
This is not glibc and I'm not Ulrich Drepper.
|
|
Monkeys!
|
|
This helps exec() and similar methods close descriptors on
shutdown.
|
|
We want more descriptive error messages and don't want
crazy stuff like floats.
|
|
We now export SOCK_NONBLOCK, SOCK_CLOEXEC constants in the Kgio
namespace to make kgio_tryaccept/kgio_accept easier-to-use.
There are also some minor internal cleanups.
|
|
It's no in the public headers, but Ruby 1.9.3 will have it and
it's still superior to rb_thread_blocking_region() even though
it's not ideal.
|
|
It's too confusing and may break binary compatibility if the
system is later upgraded.
|
|
We don't want people using the compatibility constants
since they're actually broken on systems with real accept4().
|
|
It's more reliable than relying on IO::NONBLOCK and
Fcntl::FD_CLOEXEC constants. The existing constants are not
guaranteed to be equivalent to what accept4() takes even
though the current Linux implementation does it this way.
|
|
my_fileno() may change errno on some Rubies
|
|
We support IPv6, not just IPv4
|
|
It's there for kgio_wait_readable
|
|
In case the toolchain can't test the feature properly
or Ruby is upgraded and the symbol is added.
|
|
Some installations of Ruby clobbered my usual CFLAGS=-Wall
|
|
IO.select can handle fd >= 1024 safely in some Rubies while
fd_set may not. We could use rb_thread_fd_select(), but
rb_wait_for_single_fd() is available now so the former
is not worth the maintenance hassle.
|
|
Kgio::File may be used to open FIFOs, so non-blocking
I/O is still useful in that context.
|
|
It is possible but unlikely to get ENOMEM on open(2),
so try to GC away some files.
|
|
New feature in 2.5, we now have 100% documentation again.
|
|
New features are better if they're documentated.
|
|
Non-profit TLD is better sounding for a Free Software
project.
|
|
|
|
* 2.4-stable:
kgio 2.4.2 - OpenSolaris build fix
extconf: -lnsl and -lsocket checks for OpenSolaris
|