Re: [netrexx-pipelines] specs bug?

[René J. <rvj...@xs...>]

Hi Marc,

no, this is no good and needs fixing. On VM Pipelines the output is the same as the 4-10 case: none.
So we have something to trace and fix. If you could open an issue at https://github.com/RexxLA/NetRexx/issues then whoever is going to work on it can assign themselves and avoid we are doing duplicate work. If I am going to fix it, I will check the issue first.

best regards,

René.

> On 6 Feb 2023, at 12:03, Marc Remes <re...@gm...> wrote:
> 
> Is this expected behaviour? (running with latest 4.05 beta updates)
> 
> $ pipe 'literal 123 | specs 1-10 1 |  cons '
> 123
> $ pipe 'literal 123 | specs 2-10 1 |  cons '
> 23
> $ pipe 'literal 123 | specs 3-10 1 |  cons '
> 3
> $ pipe 'literal 123 | specs 4-10 1 |  cons '
> 
> $ pipe 'literal 123 | specs 5-10 1 |  cons '
> netrexx.lang.BadArgumentException: Argument -1 < 0
> 	at netrexx.lang.Rexx.intcheck(Rexx.java:920)
> 	at netrexx.lang.Rexx.substr(Rexx.java:1458)
> 	at netrexx.lang.Rexx.substr(Rexx.java:1452)
> 	at p5e8377b_specs_2.run(p5e8377b.java:173)
> 	at org.netrexx.njpipes.pipes.ThreadPool.run(ThreadPool.java:76)
> 	at java.base/java.lang.Thread.run(Thread.java:1589)
> ThreadQ Thread[#27,Thread-1,5,njPipes]
> ThreadQ Thread[#27,Thread-1,5,njPipes]
> Exiting due to uncaught Exception Argument -1 < 0
> ThreadQ Thread[#27,Thread-1,5,njPipes]
> Exiting due to uncaught Exception Argument -1 < 0
> ThreadQ Thread[#29,Thread-3,5,njPipes]
> Exiting due to uncaught Exception Argument -1 < 0
> ThreadQ Thread[#29,Thread-3,5,njPipes]
> ThreadQ Thread[#29,Thread-3,5,njPipes]
> 
> Marc
> _______________________________________________
> netrexx-pipelines mailing list
> net...@li...
> https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines