Details
- Reviewers
olasd - Group Reviewers
Reviewers - Commits
- rDWAPPS729f9bd18fc9: swh-web: Better handle aliases in snapshot content
Diff Detail
- Repository
- rDWAPPS Web applications
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Event Timeline
Build has FAILED
Link to build: https://jenkins.softwareheritage.org/job/DWAPPS/job/tox/742/
See console output for more information: https://jenkins.softwareheritage.org/job/DWAPPS/job/tox/742/console
Build is green
See https://jenkins.softwareheritage.org/job/DWAPPS/job/cypress-diff/344/ for more details.
Build is green
See https://jenkins.softwareheritage.org/job/DWAPPS/job/tox/744/ for more details.
Build is green
See https://jenkins.softwareheritage.org/job/DWAPPS/job/cypress-diff/346/ for more details.
There's nothing in the spec that would prevent having to follow a chain of aliases, but I guess a single step resolution is good enough for now.
I suggest that at some point the "branch alias resolution" moves to the swh.storage.algorithms.snapshot module as a generic tool: I think it would make sense to have a "get the target directory for this branch on this snapshot" function, which would return the list of objects traversed up to the directory: branch aliases, releases, revisions.
This will also prepare us for the resolution of T1258.