Can no longer start REPL. Enclojure 1.4/NB 6.9.1

[Slartibartfast]

You know that bug that causes sporadic timeout errors starting a REPL?
Well, it suddenly got worse (don't ask me how). I no longer seem to be
able to create a project REPL at all. Every time, now, consistently (I
tried about 10 times in a row), it does this:

1. Java task appears in task manager, starts using 30-45% CPU
2. Nothing else happens for several seconds
3. Enclojure complains that an error was made and refuses
access to the REPL, though there is a running Java task that
appears to be the REPL task. Simultaneously that task's CPU
use drops to zero.

This is now a dealbreaker. If it isn't fixed very soon I will have no
choice but to switch to CCW or another development environment. My
ability to develop is crippled without access to a REPL.

[Eric Thorsen]

Are you loading many projects or projects with lots of jars and/or
files? I'm trying to determine if the timeout being extended might be
a temporary workaround if that is the case.
Regarding items 3, can you send me the error message?

Thanks,
Eric

> --
> You received this message because you are subscribed to the Google Groups "enclojure" group.
> To post to this group, send email to encl...@googlegroups.com.
> To unsubscribe from this group, send email to enclojure+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/enclojure?hl=en.
>
>

[Slartibartfast]

On May 10, 11:48 pm, Eric Thorsen <ethor...@enclojure.org> wrote:
> Are you loading many projects or projects with lots of jars and/or
> files?

I'm not loading anything yet at that point. This happens at the right-
click "Start Project REPL" stage, long before I get around to loading
individual files with right-click "load file"/Alt+L. All it should be
loading are the project's configured libraries, which besides JavaSE's
rt.jar are just the clojure and clojure-contrib jars at this point --
no other projects' jars, nor any third-party dependencies. (I'd ask if
you were implying that adding such would make this issue even *worse*,
but since it just today suddenly and spontaneously(!) jumped to being
maximally bad anyway, namely a 100% failure rate, it's moot.)

> I'm trying to determine if the timeout being extended might be
> a temporary workaround if that is the case.

I suggest extending it to a full minute, as a PERMANENT workaround,
and detecting if the child Java process has actually failed to start
or promptly returned with a nonzero exit status (I'm sure there are
tools for that in the standard Java API -- Executor, Process, Runtime,
etc.) and giving an appropriate error message in such instances, e.g.
capture the System.err output from the child process and report that
if it exits with a nonzero status).

> Regarding items 3, can you send me the error message?

It is the standard timeout error message (which incidentally really
does not need to take most of a 1280x1024 display's screen area to
show the salient bit -- namely, the fact that it timed out).

[Eric Thorsen]

The soonest I can get this up for you is tomorrow or the weekend.
If you are up for it, you can pull the 1.4 branch go into the repl-
client project the repl-manager.clj and the 10000 timeout to whatever
setting you want.

I am testing the change on the main trunk and attempting to correct
some bugs that came up on NB7.0 which I also hope to have up over the
weekend.

Eric

[Slartibartfast]

On May 12, 2:08 pm, Eric Thorsen <ethor...@enclojure.org> wrote:
> The soonest I can get this up for you is tomorrow or the weekend.
> If you are up for it, you can pull the 1.4 branch go into the repl-
> client project the repl-manager.clj and the 10000 timeout to whatever
> setting you want.
>
> I am testing the change on the main trunk and attempting to correct
> some bugs that came up on NB7.0 which I also hope to have up over the
> weekend.

Thank you.