[Swift-devel] Path.parse(path.toString())

[Mihael Hategan]

It's unrelated to the Path.parse issue.

var_str has no elements, but the code is assuming that it does.

On Mon, 2011-09-12 at 17:01 -0500, Ketan Maheshwari wrote:
> Hello,
> 
> 
> Today I saw this error on SCEC workflow.
> 
> 
> 
> 
> could not find variable:
> _concurrent/var_str-d9e801ee-8aca-431f-99a0-8286c452c779-13-6 [7]
> Invalid path exception org.griphyn.vdl.mapping.InvalidPathException:
> Invalid path ([7]) for var_str:string[0] - Closed for path [7]
> org.griphyn.vdl.mapping.InvalidPathException: Invalid path ([7]) for
> var_str:string[0] - Closed
> at
> org.griphyn.vdl.mapping.AbstractDataNode.getField(AbstractDataNode.java:204)
> at
> org.griphyn.vdl.mapping.file.ArrayFileMapper.map(ArrayFileMapper.java:55)
> at
> org.griphyn.vdl.karajan.lib.VDLFunction.leafFileName(VDLFunction.java:281)
> at
> org.griphyn.vdl.karajan.lib.VDLFunction.leafFileName(VDLFunction.java:270)
> at
> org.griphyn.vdl.karajan.lib.VDLFunction.filename(VDLFunction.java:187)
> at
> org.griphyn.vdl.karajan.lib.VDLFunction.filename(VDLFunction.java:175)
> at org.griphyn.vdl.karajan.lib.Stagein.function(Stagein.java:54)
> at org.griphyn.vdl.karajan.lib.VDLFunction.post(VDLFunction.java:62)
> at
> org.globus.cog.karajan.workflow.nodes.AbstractSequentialWithArguments.futureModified(AbstractSequentialWithArguments.java:208)
> at org.griphyn.vdl.karajan.DSHandleFutureWrapper
> $1.run(DSHandleFutureWrapper.java:63)
> at java.util.concurrent.Executors
> $RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor
> $Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor
> $Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> Execution failed:
> Progress:  time: Mon, 12 Sep 2011 16:50:27 -0500  Submitted:1
>  Active:17  Finished successfully:10
> 
> 
> 
> 
> Complete log for this run is:
> http://www.ci.uchicago.edu/~ketan/postproc-20110912-1642-epj1ebm1.log
> 
> 
> Swift is r5102.
> 
> 
> Regards,
> Ketan
> 
> On Fri, Sep 9, 2011 at 9:33 AM, Michael Wilde <wilde at mcs.anl.gov>
> wrote:
>         So far Im not able to re-create this problem on the prior
>         revision of 0.93.
>         
>         Im currently using this variation of the script Mihael posted
>         below:
>         
>         type file;
>         
>         type struct {
>                file b;
>                file c;
>         }
>         
>         app (struct of) echo() {
>         
>          sh "-c" "echo bee >fileb ; echo see >filec";
>         }
>         
>         struct s <ext;exec="structbug1.map">;
>         
>         s = echo();
>         
>         I discovered what I think is a new bug in the process: if the
>         shell command string contains the characters >&1 and >&2,
>         Swift complains that it cant process the intermediate xml.
>         Presumably those shell sequences are getting xml parsing
>         confused and need to be escaped.
>         
>         - Mike
>         
>         ----- Original Message -----
>         > From: "Mihael Hategan" <hategan at mcs.anl.gov>
>         
>         
>         > To: "David Kelly" <davidk at ci.uchicago.edu>
>         > Cc: "Swift Devel" <swift-devel at ci.uchicago.edu>
>         > Sent: Friday, September 9, 2011 1:31:44 AM
>         > Subject: Re: [Swift-devel] Path.parse(path.toString())
>         > On Fri, 2011-09-09 at 01:10 -0500, David Kelly wrote:
>         > > It looks like there are a few scripts in the test suite
>         which write
>         > > structs and seem to be passing.
>         >
>         > I suspect they are not staging structs out (just in).
>         >
>         > >  Do you happen to have an example script I could add to
>         the suite?
>         >
>         > type file;
>         >
>         > type struct {
>         > file b;
>         > file c;
>         > }
>         >
>         > app (struct of) echo() {
>         > bash "echo bee >1 ; echo see >2" stdout=@filename(of.b)
>         > stderr=@filename(of.c);
>         > }
>         >
>         > struct s <simple_mapper;>;
>         >
>         > s = echo();
>         >
>         > (I'm not sure if this actually works if the bug is fixed,
>         but I know
>         > it
>         > doesn't if it isn't. Anyway, you get the idea).
>         >
>         > _______________________________________________
>         > Swift-devel mailing list
>         > Swift-devel at ci.uchicago.edu
>         >
>         https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel
>         
>         
>         --
>         Michael Wilde
>         Computation Institute, University of Chicago
>         Mathematics and Computer Science Division
>         Argonne National Laboratory
>         
>         
>         _______________________________________________
>         Swift-devel mailing list
>         Swift-devel at ci.uchicago.edu
>         https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel
>         
> 
> 
> 
> 
> -- 
> Ketan
> 
> 
>