Lucio Lelii
2ea8e33987
Two follow-ups to the iterator/loop global input fix. **One propagation.** Every container path carried the parent's global inputs into its child with its own copy of the same code, and the copies drifted: the one in ExecutionsService read the unprefixed variables map through a "global." view and handed every iterator and loop child nulls, while the copy in GenericContainerExecutor read the runtime map and kept working. Both now call SubflowGlobalInputs.descriptorsFor, so there is nothing left to diverge. It also sets `multiple` on the descriptor, which neither copy did. The IODescriptor-to-kind switch had grown four identical copies for the same reason, one per descriptor-building site. It now lives on ExecutionVariableKind as forDescriptor. **A message that says something.** Starting a non-READY execution reported only "is not in READY status (CURRENT STATUS is CREATED)". For a container subflow that named an execution the user never sees and gave nothing to act on. What holds an execution back is one of three things, so notStartableReason names it: missing global inputs, missing credentials, or inputs still to provide and on which step. startContainerChild is the single point every container path starts its child from, so it frames that with the container's own name: The subflow of container 'Candidate loop' cannot start: no value for the global input 'who' and the error is filed against the container step, so the diagram points at it. Also fixed: BranchRejoinConcurrencyTest did not compile on its own (a capture conversion the Eclipse compiler rejects), which the full suite had been hiding through incremental compilation. 516 tests green. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .mvn/wrapper | ||
| src | ||
| .gitattributes | ||
| .gitignore | ||
| Dockerfile | ||
| mvnw | ||
| mvnw.cmd | ||
| ollama-preloaded-docker | ||
| pom.xml | ||
| run_service.sh | ||