- User Since
- Jul 10 2018, 12:38 PM (41 w, 2 d)
Fri, Apr 19
no need to keep the cli plugins in a dict
Add requests to requirements.txt since it does come with swh.core any more
kill the PostresHandler instead of "shuffling it around" (© olasd)
Fix commit messages
This also requires we can install only a very light base version of swh.core (typically without db or aiohttp/flask dependencies).
A possible way of doing such a thing is to have an almost empty swh.cli package that declares the main entry point: the swh command group (using click) which defines a few very command command line options (like --log-level), and a mecanism to load installed SWH cli plugins via setuptools' pkg_resources
Thu, Apr 18
This generic swh cli should be done so that is minimal dependency installed especially for "pure client" commands (e.g. swh.deposit's deposit or swh.model's identify tools).
Currently, we have:
It is these graphs we are still missing.
Tue, Apr 16
Indeed it is the object of T1428. That's why I am a bit puzzled the work you have in progress does not simply target T1356. I was expecting some response to this very task in your grafanalib based code, which I did not find. So I was wondering if I missed something, that some data where still in munin only.
Mon, Apr 15
As discussed, this task should be actually the first step of a more generic software-heritage cli client module (using HTTP based AIPs/RPCs).
LGTM but I'm not very familiar with this code.
could you explain in the commit message why this solves a cnx leak?
few minor fixes to be make, then should be ok.
Fri, Apr 12
lgtm (but I'm obviously biased)
Thu, Apr 11
Wed, Apr 10
ok but see my comment plz
Fri, Apr 5
I'm not very fond adding this kind of service in the main docker-compose file.
I would prefer a dedicated docker-compose file to be used as an override, eg: