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

feature: explicit representation of an exescript (batch) #564

Closed
shadeofblue opened this issue Jul 27, 2021 · 0 comments · Fixed by #609
Closed

feature: explicit representation of an exescript (batch) #564

shadeofblue opened this issue Jul 27, 2021 · 0 comments · Fixed by #609
Assignees
Labels
enhancement New feature or request EPIC: Maintenance

Comments

@shadeofblue
Copy link
Contributor

currently, WorkContext is connected to an activity and commands are sequentially added to it until they're committed (sent for execution).

this causes two issues:

  • side-by-side execution (and even preparation) of scripts is impossible since - because the context is the same - the scripts will interleave each other
  • implicit deploy: currently, deploy/start are added implicitly when the first script is started -> there could be a lock which would only trigger on the first sent script (and not necessarily on the first started one)

we would like to extract the Script/Batch class from the WorkContext and make it explicitly separate -> the WorkContext would still be bound to a single activity but the batches would not be part of WorkContext itself

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request EPIC: Maintenance
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants