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.

Sign up for GitHub

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

Jump to bottom

CLI option to control execution environment #6131

Closed
JaroslavTulach opened this issue Mar 29, 2023 · 0 comments · Fixed by #6171
Closed

CLI option to control execution environment #6131

JaroslavTulach opened this issue Mar 29, 2023 · 0 comments · Fixed by #6171
Assignees
@hubertp
Labels
-compiler
Milestone
Design Partners

Comments

@JaroslavTulach
Copy link
Member

The CLI should allow selecting the execution environment via a new command line argument --execution-environment and if not specified should default design. So, enso --execution-environment live would run the script within "live" mode enabling the Output behavior. This functionality would also need to be available within the cloud when running a job.
@JaroslavTulach JaroslavTulach added this to the Beta Release milestone Mar 29, 2023
@enso-bot enso-bot bot mentioned this issue Mar 30, 2023
Merged
2 tasks
@jdunkerley jdunkerley moved this from ❓New to 📤 Backlog in Issues Board Mar 30, 2023
hubertp added a commit that referenced this issue Apr 3, 2023
@hubertp
Add cli option to control environment
218f18a 
Added a fix for #6131 to allow for some testing.
@hubertp hubertp mentioned this issue Apr 3, 2023
Merged
4 tasks
@jdunkerley jdunkerley moved this from 📤 Backlog to 👁️ Code review in Issues Board Apr 4, 2023
hubertp added a commit that referenced this issue Apr 5, 2023
@hubertp
Add cli option to control environment
fe614da 
Added a fix for #6131 to allow for some testing.
hubertp added a commit that referenced this issue Apr 6, 2023
@hubertp
Add cli option to control environment
31730d2 
Added a fix for #6131 to allow for some testing.
@mergify mergify bot closed this as completed in #6171 Apr 6, 2023
@mergify mergify bot closed this as completed in 3cce3b3 Apr 6, 2023
@github-project-automation github-project-automation bot moved this from 👁️ Code review to 🟢 Accepted in Issues Board Apr 6, 2023
MichaelMauderer pushed a commit that referenced this issue Apr 25, 2023
@hubertp @MichaelMauderer
Replace IOContexts with execution env and contexts (#6171)
35d05fe 
As per design, IOContexts controlled via type signatures are going away. They are replaced by explicit `Context.if_enabled` runtime checks that will be added to particular method implementations.

`production`/`development` `IOPermissions` are replaced with `live` and `design` execution enviornment. Currently, the `live` env has a hardcoded list of allowed contexts i.e. `Input` and `Output`.

# Important Notes
As per design PR-55. Closes #6129. Closes #6131.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hubertp hubertp

Labels
-compiler
Projects
Issues Board
Archived in project
Milestone
Design Partners
Development

Successfully merging a pull request may close this issue.

Replace IOContexts with execution env and contexts enso-org/enso
3 participants
@hubertp @jdunkerley @JaroslavTulach