Remove outdated part about listers database and use swh CLI in
README for executing a lister instead of raw Python code.
Details
Details
- Reviewers
ardumont - Group Reviewers
Reviewers - Commits
- rDLSe72c15e97a2e: docs: Update listers execution instructions
Diff Detail
Diff Detail
- Repository
- rDLS Listers
- Branch
- update-lister-doc
- Lint
No Linters Available - Unit
No Unit Test Coverage - Build Status
Buildable 19046 Build 29519: Phabricator diff pipeline on jenkins Jenkins console · Jenkins Build 29518: arc lint + arc unit
Event Timeline
Comment Actions
Build is green
Patch application report for D5031 (id=17927)
Rebasing onto 1803b707e4...
Current branch diff-target is up to date.
Changes applied before test
commit e72c15e97a2e2f6269a9fe3019e118fee0321395 Author: Antoine Lambert <antoine.lambert@inria.fr> Date: Fri Feb 5 12:35:37 2021 +0100 docs: Update listers execution instructions Remove outdated part about listers database and use swh CLI in README for executing a lister instead of raw Python code.
See https://jenkins.softwareheritage.org/job/DLS/job/tests-on-diff/246/ for more details.
Comment Actions
lgtm
docs/run_a_new_lister.rst | ||
---|---|---|
87 | You may also want to propose something like: select * from listed_origins lo inner join listers l on lo.lister_id=l.id where l.name='cgit' and l.instance_name='eclipse' limit 10; |
docs/run_a_new_lister.rst | ||
---|---|---|
87 | I will keep a simple query here, the idea is just to indicate in which database and table the data can be found. |
docs/run_a_new_lister.rst | ||
---|---|---|
87 | yes, i guessed as much ;) why the "may". In my staging deployments (more than 1 lister), that query was too simple and returned too much. |