Version 0.0.1

[GitHK]

What do these changes do?

Add a base library to be used for control cases.
NOTE: this package was build using cookiecutter-hypermodern-python for convenience.

How does it work?

• The osparc_control package provides an easy way to define a supported interface by providing a list of CommandManifest.
• A CommandManifest is the interface(signature) of the supported command.
• Each request from a remote is validated against CommandManifest. A CommandReceived confirmation is always send to each command. The requester expects this command to be delivered (this is required to avoid the requesting part being stuck awaiting forever if the remote part is not running). A 1 minute interval is defined to detect this situation.
• It supports 3 types of commands defined by CommandType:

class CommandType(str, Enum):
    # the command expects no reply
    WITHOUT_REPLY = "WITHOUT_REPLY"

    # the command will provide a reply
    # the user is require to check for the results
    # of this reply
    WITH_DELAYED_REPLY = "WITH_DELAYED_REPLY"

    # the command will return the result immediately
    # and user code will be blocked until reply arrives
    # used for very fast replies (provide data which already exists)
    WITH_IMMEDIATE_REPLY = "WITH_IMMEDIATE_REPLY"

How to test

You require poetry on your system, please make sure it is installed.

In a virtualenv install dev dependencies

make install-dev

Run suite with python 3.6 and nox.

make nox-36

If you do not have python 3.6 on your system feel free to run with a different python interpreter by changing the below command (replace 3.6 with your version of python:

nox -p 3.6

Examples

Please follow the updated README.md

What changed

• examples are now tested
• replaced sphynx with docsify
• documentation will be available at https://itisfoundation.github.io/osparc-control/ once this is merged to master

Related issues

• coupling API osparc-issues#555

[pcrespov]

Why dont' you use subprocess.run instead? the latest versions of python provide this more convenient helper that is far more readable and has preconfigured the most common setups. Using raw Popen can be sometimes errorprone ... (we already had this discussion several times... :-) )

[GitHK]

Not what I wanted or needed. From the docs

Run the command described by args. Wait for command to complete, then return a CompletedProcess instance.

I need to start 2 scripts and wait for them to complete.

[pcrespov]

but these do not run in parallel as you claim in assert_run_in_parallel , right?

[GitHK]

Yes they do run in parallel, otherwise it would not be possible for example/2_base_time_add to finish.
In the above loop I wait for the process to provide a returncode, meaning it finished execution.

Here I fetch the standard output.

[KZzizzle]

Awesome! let's get this in!

[sanderegg]

these entries are amazingly clear 🤣

[elisabettai]

It looks good to me! Looking forward to testing it.