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

Need to integrate async #2

Open
vsoch opened this issue May 14, 2020 · 3 comments
Open

Need to integrate async #2

vsoch opened this issue May 14, 2020 · 3 comments

Comments

@vsoch
Copy link
Owner

vsoch commented May 14, 2020

Right now we are issuing a command, waiting for the result, etc. We will need to be able to do this to launch a job /process and then come back to check it later. I want to develop the more core features of the library first.

@vsoch
Copy link
Owner Author

vsoch commented May 15, 2020

A few options:

I think a lot of these solutions would work well given a constantly running server (e.g., the web interface) but for just the command line version, it would be more "run on demand."

@vsoch vsoch mentioned this issue May 22, 2020
1 task
@vsoch
Copy link
Owner Author

vsoch commented May 30, 2020

Picking up conversation from #24 - @yarikoptic time wise, I think this will be best to develop when we are actively working on an executor that warrants needing more time. I think we will want to:

  • test a few strategies (different async libraries, for examples) and decide on the best one
  • if it's appropriate to make as a default (using or not) then set this for the base executor, allow subclass executors to change the default if they deem fit
  • if appropriate, allow the user to specify using one or the other (e.g., in gridtest I run things default in parallel, and give an option to run --serial which is useful for debugging.

I'd like to first merge #32, then address the logging and system exits, and then possibly we can get back to this when we develop an executor that warrants it (e.g., datalad or repronim).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant