Norman Walsh
Norman Walsh
That is definitely weird. I'll take a look.
The root cause is Saxon [bug #5691](https://saxonica.plan.io/issues/5691) but I can work around it in the short term.
Fixed in 1.5.1, I believe.
Yeah, there are clearly some issues here.
I'm afraid it doesn't ring a bell. Can you run with -D and send me the stack trace?
On the current development trunk, that pipeline fails because the result port of ex:identity is not declared to allow a sequence. Other than that, I agree it does look like...
I have to observe however, that if you passed all of those parameters and inputs to a document that actually _used_ the parameters, that step would see the right values....
The sequence was required on the output. The output port isn't a parameter port.
Is there anything I can do to help triage this? I've recreated the problem with the five minute sample application from the .NET documentation.
Simple example of reproducing the bug: ``` $ cd /tmp /tmp $ dotnet --info .NET SDK (reflecting any global.json): Version: 6.0.201 Commit: ef40e6aa06 Runtime Environment: OS Name: Mac OS X...