- User Since
- Sep 7 2015, 3:43 PM (263 w, 4 d)
As @olasd pointed out, async is a keyword so let's not use it as module name :-)
For whoever who want to work on this (and on doc restructuring in general), I recommend to watch this talk: https://www.youtube.com/watch?v=t4vKPhjcMZg , which provides a good taxonomy of the kind of docs that exist. Our GSoD 2019 application page also contains a lot of useful related work.
Wed, Sep 23
we have rewritten this from scratch and we will commit it separately
Tue, Sep 22
Caveat: as this results in an API change (I think), it should be announced on the swh-devel mailing list before deployment.
Mon, Sep 21
Sun, Sep 20
I can confirm that with the current master HEAD of swh-loader-core (452fa224f9ca635a979cf1a8e98c88bb560ca98a), loading of the Linux kernel repo no longer OOM.
(It failed after ~24 hours, but apparently for unrelated reasons.)
Sat, Sep 19
This is fine, and better than the status quo.
(We should in theory also mention the other applicable copyright notices at the beginning of the file, but we weren't doing that before either, so this change LGTM.)
this has been fixed a while ago by D2669
Fri, Sep 18
- uniform tox.ini and setup.cfg with python module template
blackify all module, rather than just test_vault.py
Thu, Sep 17
(I was initially surprised by the mixing together of "import" lines with "from ... import" ones, but upon reflection it makes a lot of sense, because one might have to switch between the two forms, and it's silly to have to move the line back and forth between import blocks when that happens.)
this has been addressed, and in a more general way that works for any SWHID, in D2582
Very likely the same issue, thanks @ardumont !
Given what @olasd said in that issue (the ingestion logic having remained pretty much the same since ever), and that I can confirm linux.git was loading just fine on my laptop no more than a year ago, the increased memory usage probably comes from elsewhere.
Anyway, it looks like a potentially important issue, so I'm raising priority and also removing the association with the docker env (as you could also reproduce this on staging).
Wed, Sep 16
I think this is (reasonably) done now, please check and close it.
We have now a newer version of the compressed graph (2020-05-20), but it's not yet running on granet (I *think*, and, lacking T2579, I haven't checked).
Please make granet run that version of this task and close this task. (Or just close this task if it's already done.)
Tue, Sep 15
looks great in general!
just a few nits here and there (and possibly a separate issue to file for the sane default part)