Legacy CLI pull: SPEC_ERROR: All mapping items must start at the same column
Open
Nobody has claimed this yet.
DevX
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
Error when trying to pull joseph-demo from staging app right now:
SPEC_ERROR: All mapping items must start at the same column at line 78217, column 1:
};
^
at extractJobsToDisk (file:///home/joe/.local/share/pnpm/global/5/.pnpm/@openfn+deploy@0.11.2/node_modules/@openfn/deploy/dist/index.js:710:11)
at async pullHandler (file:///home/joe/.local/share/pnpm/global/5/.pnpm/@openfn+cli@1.13.3/node_modules/@openfn/cli/dist/process/runner.js:2231:25)
at async parse (file:///home/joe/.local/share/pnpm/global/5/.pnpm/@openfn+cli@1.13.3/node_modules/@openfn/cli/dist/process/runner.js:2409:12)
This might be something about the yaml file being too big?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the legacy pull flow through extractJobsToDisk, pullHandler, and parse in the @openfn/deploy and @openfn/cli stack traces. Reproduce the pull for joseph-demo from staging and inspect the YAML around line 78217. Done means the pull completes without the mapping-column parser error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100