I applied this.
-Tom
On Tue, 30 May 2006, Evan Buswell defenestrated me:
> I think this patch should fix the buffering problem. Turns out C Ruby
> doesn't tag an io stream as buffered until a *read* buffering operation
> happens; I was tagging it for *write* as well.
>
> Let me know if it wo
I think this patch should fix the buffering problem. Turns out C Ruby
doesn't tag an io stream as buffered until a *read* buffering operation
happens; I was tagging it for *write* as well.
Let me know if it works.
Evan
Thomas E Enebo wrote:
> A simple hack which may or may not work is to remo
As long as the code doesn't *actually* mix the two IO modes, you should
be able to remove checkBuffered as an ugly temporary hack just to get
the piece of code running. However, if it does mix buffered and
unbuffered IO calls, this might cause spurious bugs.
The reason this is happening is that w
A simple hack which may or may not work is to remove the
checkBuffered() call from sysread in IOHandlerNio.java. If things
work with that commented out then we can work from that.
-Tom
On Sun, 28 May 2006, Ola Bini defenestrated me:
> Hi.
>
> Now I'm trying to get remote gem installation to
Evan's recent changes to use nio for socket stuff is very
likely the culprit. I will take a look to see how easy this
is to fix.
Also I have not been around much the last few days (getting some
errands done before I fly out to a conference). So I apologize for
being quiet.
-Tom
On Sun, 28
Hi.
Now I'm trying to get remote gem installation to work, but immediatly
ran into an error, in a part which used to work before. Is this because
of the resent work on IO in general?
Attempting local installation of 'rails'
Local gem file not found: rails*.gem
Attempting remote installation of 'r