- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Sep 16 2020
Sep 10 2020
Feb 25 2020
Feb 24 2020
Feb 13 2020
Feb 11 2020
Feb 7 2020
I think it qualifies, yes
@vlorentz I'm not sure it is an easy hack, could you review the task and decide?
Feb 4 2020
Yes, but you should just open a diff instead.
And does Jenkins also run code in non-master branches through the pipeline?
Feb 3 2020
and apologies for the delay.
Feb 2 2020
Thanks for the detailed reply 🙂, and apologies for the delay. Things are clearer now 👍
Feb 1 2020
hey, I would like to contribute.
The pytest tests are succeeding in the swh-indexer module, but failing in some other modules. Since this issue pertains to only the swh-indexer module, it shouldn't cause problems, right?
Hi, I'd like to take up this issue as my first issue here :) . But before I take it up, I just had a few queries:
Jan 29 2020
Jan 27 2020
Jan 23 2020
sample with our shiny sentry: https://sentry.softwareheritage.org/share/issue/f4a40625783b4a5588980005ddc5a5e6/
Jan 22 2020
Jan 13 2020
Dec 20 2019
Dec 3 2019
Dec 2 2019
Nov 22 2019
Fixed by D896.
Nov 14 2019
Does it still happen? The journal client changed a lot since this task was open, including switching backend library.
Nov 8 2019
Fixed by @olasd
Nov 5 2019
Sep 30 2019
That's the postgresql statement_timeout variable that we set for some methods on the storage backends.
In T1788#37373, @ardumont wrote:We can investigate 2 things:
- check postgresql options to kill queries that takes too long (solely indexer-db right now) -> and find some way to report those
Sep 27 2019
We can investigate 2 things:
- check postgresql options to kill queries that takes too long (solely indexer-db right now) -> and find some way to report those
- push the proxy client storage idea (started within the T1389 for the storage, currently wip) up to the indexer-storage.
Sep 24 2019
Note: ... comments stack pop ... (-> been there a while apparently)
Sep 6 2019
In the end, it was missing initialization data steps.
Sep 5 2019
current status:
Jul 10 2019
Jul 9 2019
I went through all the tests in test_storage.py. It appears that only content_fossology_license_get needs to be refactored. All other storage methods return a dictionary or a list of dictionaries, where each dictionary has multiple keys.
Jul 8 2019
Jul 7 2019
I am familiar with the web APIs and I went through the discussion in T782. When you say output a single dictionary, I believe you mean something like this
{ sha1: [ {tool: TOOL, licenses: [licences]}, {tool: TOOL, licenses: [licences]} ],
Jul 3 2019
- swh-indexer-journal-client: Update cli to latest version
- swh-indexer-journal-client: Fix configuration change
Jun 25 2019
Jun 24 2019
Jun 20 2019
D1582 has been pushed the task can be closed
Jun 18 2019
Jun 15 2019
All columns commented in swh-scheduler, waiting review.
Some columns for swh-storage required a small discussion to frame appropriate comments.
Jun 14 2019
All columns are already commented in swh-indexer
Have added a few comments in D1582
Jun 13 2019
The latest upgrade is 136.sql while the version in 30-swh-schema.sql is 133. Should I name the next upgrade 137?
there seems to be an inconsistency between sql/upgrades and latest sql version in swh-storage. The latest upgrade is 136.sql while the version in 30-swh-schema.sql is 133. Should I name the next upgrade 137?
is there anything left to be done to close the task?
Jun 12 2019
modules swh-scheduler, swh-indexer, swh-storage, all seem to have column comments written in 30-swh-schema.sql
Can you provide a few more details so I can work on this? Maybe which packages will be affected and what is expected in the comments.
Jun 7 2019
In the mean time, i've stopped those indexers as this impacts other (i see transactions piling-up).
May 25 2019
May 22 2019
Apr 24 2019
We should investigate why they are there.
This is now done, aside from a minor issue noted below:
softwareheritage-indexer=# select count(*) from revision_intrinsic_metadata where metadata = '{"@context": "https://doi.org/10.5063/schema/codemeta-2.0"}'::jsonb; count ------- 0 (1 row)