George Jahad writes:
> Hmmm. I'm seeing different behaviour. When I run your code
> untouched, I never get the "unchunked" error. Instead, I see a bunch
> of garbage printed after the echoed "hello" like so:
>
> echo "hello" | ng nailgun.Example
>
> hello
> ^...@^@^...@^@^...@^@^...@^@^...@^@
Hmmm. I'm seeing different behaviour. When I run your code
untouched, I never get the "unchunked" error. Instead, I see a bunch
of garbage printed after the echoed "hello" like so:
echo "hello" | ng nailgun.Example
hello
^...@^@^...@^@^...@^@^...@^@^...@^@^...@^@^...@^@^...@^@^...@^@^...@^@^
George Jahad writes:
> I think it is just an input stream encoding problem. I think if you
> change this line:
> (copy (-> context .in) out)
>
> to this:
> (copy (-> context .in InputStreamReader.) out)
>
> it will work.
Thanks, but that gives the same result. =\
Contributing to the p
Hey Phil:
I think it is just an input stream encoding problem. I think if you
change this line:
(copy (-> context .in) out)
to this:
(copy (-> context .in InputStreamReader.) out)
it will work.
George
On Jul 6, 5:06 pm, Phil Hagelberg wrote:
> So a common counter to "the VM startup
So a common counter to "the VM startup time is so bad" problem is to use
Nailgun for a long-running server process. I've gotten this working in
some respects, but I get a "Unexpected chunk type 83 ('S')" error quite
often when I'm trying to read from the stdin that the nailgun context
provides.
