Bo

However, for whatever reason, sometimes the pypy version freezes after the workflow completes ``` $ time bin/sos run test -s force INFO: Running default: INFO: Workflow default (ID=333af83f177dde30) is executed...

The pypy version of SoS falls to an indefinite loop when running [this example from #1213 ](https://github.com/vatlab/SoS/issues/1213#issuecomment-480353003). It is therefore necessary to test pypy after its gets out of beta.

"Production" in the old days means robustness and backward compatibility, but I have seen the latter being tossed around with less emphases. I tend to say we can declare production...

> Oh, local .sos has been removed. `./.sos` was not something documented and users were not encouraged to explore it. With the removal of `sos pack/unpack` `.sos` was better stay...

Yes, those were exactly the motivations....

Had a quick look at the issue list and they are 1. features that could be nice to have, but too complicated to implement now. 2. bugs that cannot be...

Ideally it should be something like ``` Pulling docker image gaow/gatk3:2.0 ... ``` then after a while ``` Pulling docker image gaow/gatk3:2.0 ...... done. ``` but this is difficult to...

Sorry, I created this ticket from my cellphone without details. I have updated the ticket.

In terms of comparison between "workers" of sos and ipyparallel, I would emphasize that 1. sos' workers are used to execute different nodes of DAG. The worker loads are heterogeneous...

Yes, the "mini-cluster" approach of nextflow means it has some built-in load balancing features and we generally avoids this problem by letting others to manage the execution of large amount...