Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CLI: impose limits #622

Open
josephjclark opened this issue Mar 11, 2024 · 0 comments
Open

CLI: impose limits #622

josephjclark opened this issue Mar 11, 2024 · 0 comments
Labels
UX UX and DevX things

Comments

@josephjclark
Copy link
Collaborator

josephjclark commented Mar 11, 2024

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.

@github-project-automation github-project-automation bot moved this to New Issues in v2 Mar 11, 2024
@christad92 christad92 moved this from New Issues to Backlog in v2 Mar 17, 2024
@josephjclark josephjclark added the UX UX and DevX things label Apr 3, 2024
@josephjclark josephjclark changed the title CLI: enable optional memory limit CLI: impose limits Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
UX UX and DevX things
Projects
Status: Backlog
Development

No branches or pull requests

1 participant