And uses the new pagination scheme, instead of origin ids.
Details
Diff Detail
- Repository
- rDSTO Storage manager
- Branch
- origin_list
- Lint
No Linters Available - Unit
No Unit Test Coverage - Build Status
Buildable 9787 Build 14451: tox-on-jenkins Jenkins Build 14450: arc lint + arc unit
Event Timeline
Build is green
See https://jenkins.softwareheritage.org/job/DSTO/job/tox/804/ for more details.
swh/storage/in_memory.py | ||
---|---|---|
1159 | Why don't you add type here and not within the docstring? | |
1164 | I thought this was to be named count? | |
1169 | retrieving | |
swh/storage/storage.py | ||
1707 | same remark than for in-memory implementation (type, name, typo). | |
1710 | Why do we force the string type here? | |
1724 | Why don't you change the db.origin_get_range implementation so that it retuns what you want instead? |
swh/storage/in_memory.py | ||
---|---|---|
1159 | Because I wrote that diff in mid-november and didn't touch it since; and we still used Python 3.5 at the time. I'll have to rebase it | |
1164 | Yeah I guess we're not consistent here. I have a small preference for limit, sorry for asking the change on the other diff, I didn't realize the inconsistency | |
swh/storage/storage.py | ||
1710 | Because it's an opaque token, so clients shouldn't know what it actually contains so we can change it at any time. (eg. for Cassandra, it will be a large byte array) | |
1724 | Because I need the origin id to compute the next_page_token. |
Build has FAILED
Link to build: https://jenkins.softwareheritage.org/job/DSTO/job/tox/837/
See console output for more information: https://jenkins.softwareheritage.org/job/DSTO/job/tox/837/console
Build is green
See https://jenkins.softwareheritage.org/job/DSTO/job/tox/838/ for more details.
Build is green
See https://jenkins.softwareheritage.org/job/DSTO/job/tox/839/ for more details.
Build is green
See https://jenkins.softwareheritage.org/job/DSTO/job/tox/840/ for more details.
swh/storage/in_memory.py | ||
---|---|---|
1164 | Well, i don't mind ;) What's the conclusion though, shall we stay on limit or use count? |
Looks good
we need to decide whether we want to use count or limit.
We are not consistent yet.
(We are getting consistent on the page_token as an optional string though, yeah ;)