Skip to content

fix(tapis): skip FIXED inputs in job submission#116

Merged
mosoriob merged 2 commits into
masterfrom
fix-tapis-fixed-input
May 3, 2026
Merged

fix(tapis): skip FIXED inputs in job submission#116
mosoriob merged 2 commits into
masterfrom
fix-tapis-fixed-input

Conversation

@mosoriob
Copy link
Copy Markdown
Contributor

@mosoriob mosoriob commented May 3, 2026

Summary

  • TapisJobService.createJobFileInputsFromSeed threw Component input not found when an app fileInput had inputMode: FIXED. FIXED inputs are locked by the app definition (sourceUrl pre-set) and have no entry in model.input_files, so the lookup failed.
  • Tapis injects FIXED inputs at submission from the app definition. They must be omitted from the job request.
  • Added an early skip for inputMode === FIXED plus regression tests for FIXED-only and mixed (OPTIONAL+FIXED) apps.

Test plan

  • npx jest src/classes/tapis/adapters/tests/jobs.test.ts — 6/6 pass
  • npx jest src/classes/tapis — 19/19 pass

mosoriob added 2 commits May 3, 2026 12:00
FIXED inputs are locked by the app definition; Tapis injects them
from the app at submission. createJobFileInputsFromSeed previously
required every app fileInput to have a matching model.input_files
entry, throwing "Component input not found" for FIXED inputs since
they are not exposed to the model component.

Skip FIXED inputs in the job request (Tapis fills them in).
@mosoriob mosoriob merged commit efdaf7f into master May 3, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant