Skip to content

ForExecutorBuilder missing null check on for.in (required field) #1625

Closed

Description

@mathecruz

ForExecutorBuilder.buildCollectionFilter() dereferences task.getFor().getIn() without a null check. When in is null (a ForTask built programmatically without setting in), this throws a raw NullPointerException with no helpful context.

Per the Open Workflow specification, for.in is a required field. The JSON Schema in
types/src/main/resources/schema/workflow.yaml correctly declares required: [ in ], and the ValidationReader enforces this for YAML/JSON workflows.

However, programmatically-built workflows bypass schema validation entirely, so the in requirement is not enforced.

Activity

  1. added a commit that references this issue on Aug 14, 2026
    87d767a
  2. added a commit that references this issue on Aug 31, 2026
    307eb07
  3. added theissue type on Oct 6, 2026
  4. changed the issue type fromtoon Oct 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions