[kepler-dev] [Bug 3774] - Hello World demo causes UI to become unresponsive and require restart

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=3774





------- Comment #3 from sbowers at ucdavis.edu  2009-01-23 13:04 -------

(In reply to comment #2)
> The odd thing is that if you set up a different network with an SDF Director
> with interations set to zero, for example, a File Reader going into a text
> display, the UI does not freeze and you are able to stop it out of the loop. 
> The problem is not a function of SDF Director's iterations set to 0, there is
> something else there.

Yes -- this is because of the nature of the FileReader actor. Of course, the
workflow you describe is very different, and here if you were to set the
iterations parameter of SDF to 1 you probably would not get the behavior you
desire.  

> Second, if the default configuration of a module leads the program to an
> unrecoverable state without any warning at all, I would very much call that a
> bug, not a documentation problem.

You might enter a new bug for what you would like to see here.  For instance,
it sounds like you might want to change the default configuration of the String
Constant actor to have the firingCountLimit be set to 1.  Alternatively, this
might be a larger issue in which the solution to the bug is that the default
configuration of all actors should not result in an "unrecoverable state"
within Kepler w.r.t. infinitely running workflows.  

However, as I read your original bug report -- it sounds like you tried to
recreate the workflow, and in doing so, didn't carry over the various parameter
settings which led to the workflow running essentially in an infinite loop.
However, the actual Hello World demo does not have this problem, which is why I
think at least for this bug, it is a documentation issue.