🔧 dask compatible requirements listings

[pcrespov]

What do these changes do?

PROBLEM: The interaction between dask actors (i.e. client/scheduler/worker) demands a certain compatibility between libraries installed in different counterparts

SOLUTION: this PR provides listings for different type of clients under services/dask-sidecar/requirements/_dask*.txt that ensure compatibility (i.e. are in sync) with worker and scheduler services build within services/dask-sidecar, i.e.

• in jupyterlab use services/dask-sidecar/requirements/_dask-complete.txt
• in director2 use services/dask-sidecar/requirements/_dask-distributed.txt

Other changes:

• pip-compile now strips extra labels from frozen requirements. (TODO: apply these changes to entire repo in a separate PR)
• uses long version of pip install CLI options to make it more readable

Related issue/s

provides minimal dask reqs for PR #2418

How to test

To test reqs compatibility

make devenv
cd services/dask-sidecar
make install-dev
make test-dev-unit

and now can update requirements and retest

cd services/dask-sidecar/requirements
make touch
make reqs
cd ..
make install-dev
make test-dev-unit

[codecov]

Codecov Report

Merging #2420 (8f6761d) into master (1c816d3) will increase coverage by 0.0%.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #2420   +/-   ##
======================================
  Coverage    75.4%   75.5%           
======================================
  Files         560     560           
  Lines       20868   20868           
  Branches     2018    2018           
======================================
+ Hits        15753   15763   +10     
+ Misses       4580    4573    -7     
+ Partials      535     532    -3     

Flag	Coverage Δ
integrationtests	66.3% <ø> (+<0.1%)	⬆️
unittests	69.2% <ø> (+<0.1%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
...erver/src/simcore_service_webserver/director_v2.py	78.7% <0.0%> (+0.7%)	⬆️
...ages/service-library/src/servicelib/aiopg_utils.py	90.8% <0.0%> (+3.0%)	⬆️
...webserver/computation_comp_tasks_listening_task.py	89.7% <0.0%> (+6.1%)	⬆️

[sanderegg]

great!

[GitHK]

👍 just a minor change request

[GitHK]

Could you move these outside of this function?

[pcrespov]

Do you have a special reason? I find it more clear inside of the only function it uses it. Short local functions are very common and useful: I can take advantage of e.g. the scope or shorter names . Generally, if I move these functions outside, i loose both: I would need to add more parameters and have longer names to avoid collisions and make it more clear in a wider context.