fix(workflows): fan-in validate() rejects non-mapping output#3349
Merged
Conversation
FanInStep.validate() only checked wait_for, so a non-mapping 'output'
(a list or scalar) validated clean; execute() then silently coerces it
to {}, so the author's declared aggregation keys vanish with COMPLETED
status and no diagnostic. Reject a non-mapping output at validation,
mirroring the command-step (github#3262) non-mapping fix. execute()'s
defensive coercion is left in place for unvalidated callers.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request closes a validation/execute contract gap in the workflow fan-in step by ensuring FanInStep.validate() rejects a non-mapping output configuration (which execute() would otherwise silently coerce to {} and drop user-declared aggregation keys).
Changes:
- Add
FanInStep.validate()check to requireoutputbe a mapping when present, with a clear type-specific error message. - Add unit tests covering rejection of non-mapping
outputvalues and acceptance of mapping/absentoutput.
Show a summary per file
| File | Description |
|---|---|
src/specify_cli/workflows/steps/fan_in/__init__.py |
Adds validation to reject non-dict output configs, preventing silent loss of aggregation configuration. |
tests/test_workflows.py |
Adds regression tests ensuring invalid output shapes are rejected and valid/absent output is accepted. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 0
- Review effort level: Low
Collaborator
|
Thank you! |
kanfil
added a commit
to tikalk/agentic-sdlc-spec-kit
that referenced
this pull request
Jul 8, 2026
Upstream commits merged (9): - 0151d23 agy honors SPECKIT_INTEGRATION_AGY_EXTRA_ARGS (github#3347) - fb796c2 shell step validate() rejects non-string run (github#3348) - 220e6fc fan-in validate() rejects non-mapping output (github#3349) - 12faf7b workflow run/resume errors to stderr under --json (github#3352) - d5ba062 bundle update uninstalls dropped components (github#3353) - f1a8d8f release 0.12.7, begin 0.12.8.dev0 (github#3398) - 10d4bca guard _sha256 against unreadable managed files (github#3376) - a307894 return None on malformed GHES port (github#3379) - 882e1e9 exit cleanly on malformed IPv6 URLs in add commands (github#3369) Conflict: presets/_commands.py — combined IPv6 try/except + _esc() with fork accent() theming. Assisted-by: OpenCode (model: glm-5.2, autonomous)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
FanInStep.validate()only validateswait_for— it never checksoutput. Butexecute()does:So a non-mapping
output(a YAML list or scalar) validates clean, then the author's declared aggregation keys are silently discarded at run time — the step returnsCOMPLETEDwith an empty aggregation and no diagnostic. Reproduced on main @bba473c:validate({'id':'j','wait_for':['a'],'output':['{{ x }}']})returns[].Fix
Reject a non-mapping
outputat validation, mirroring the command-step (#3262) non-mapping input/options fix.execute()'s defensive coercion is intentionally left in place for callers that skip validation.Testing
test_validate_rejects_non_mapping_outputparametrized over a list, a string, and an int → all report'output' must be a mapping. Fails before (validate returns[]— verified by source-stash), passes after.test_validate_accepts_mapping_or_absent_output: a mapping and an omittedoutputreturn[].TestFanInStep: 9 passed.uvx ruff checkclean.AI Disclosure
Found and fixed with Claude Code (Claude Fable 5) under my direction. AI flagged fan-in as the remaining step with a validate-vs-execute shape gap; I reproduced the silent key-drop, verified fail-before/pass-after, and reviewed the diff.