CLI: impose limits
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
A common problem is that a workflow runs fine in the CLI, but when its migrated to platform (v1 or v2) it starts breaking because of memory limits (dataclip size, runtime memory)
The CLI should:
- By default, impose the same limits as Lightning
- When it blows up due to limits, post a very friendly message saying how to disable the limits
- Provide options in workflow, arguments and env vars to set the limits
- Provide an easy means to disable all limits
- Provide an easy means to sync limits with a lightning project (or with keywords, like "community" or "pro"
This helps prevent problems when a perfect workflow in CLI needs to be re-written to work on platform.
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 mapping where the CLI handles workflows, arguments, and environment variables, then compare the requested limits with the corresponding Lightning platform limits. Define how default enforcement, friendly limit errors, disabling limits, and syncing with Lightning projects or keywords should work before identifying the affected tests and entry points.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100