Changes are to be made in "Storage.content_get" to support the slicing of the data of full blob returned to it.
To execute this , two new parameters are added as an argument to the function "content_get()" to specify the rand of bytes that the caller requires
and also to pass them to the obstorage. Same changes have been made to both the files "swh/storage/in_memory.py" and "swh/storage/storage.py"
Details
- Reviewers
Sowmya - Group Reviewers
Reviewers - Required Signatures
L3 Software Heritage Contributor License Agreement, version 1.0
Diff Detail
- Repository
- rDSTO Storage manager
- Branch
- data_slicing
- Lint
No Linters Available - Unit
No Unit Test Coverage - Build Status
Buildable 5163 Build 6954: tox-on-jenkins Jenkins Build 6953: arc lint + arc unit
Event Timeline
Build has FAILED
Link to build: https://jenkins.softwareheritage.org/job/DSTO/job/tox/310/
See console output for more information: https://jenkins.softwareheritage.org/job/DSTO/job/tox/310/console
The parameter in the function (i.e. start and end) were not specified in earlier version, so correcting it.
Build has FAILED
Link to build: https://jenkins.softwareheritage.org/job/DSTO/job/tox/311/
See console output for more information: https://jenkins.softwareheritage.org/job/DSTO/job/tox/311/console
Build has FAILED
Link to build: https://jenkins.softwareheritage.org/job/DSTO/job/tox/312/
See console output for more information: https://jenkins.softwareheritage.org/job/DSTO/job/tox/312/console
Build has FAILED
Link to build: https://jenkins.softwareheritage.org/job/DSTO/job/tox/313/
See console output for more information: https://jenkins.softwareheritage.org/job/DSTO/job/tox/313/console
Thanks for the contribution but there is still some actions required from your side in order for the Software Heritage developers to review your changes:
- sign our contributor license agreement
- rebase your changes on origin/master and update that diff using arc diff --update D1363
Build is green
See https://jenkins.softwareheritage.org/job/DSTO/job/tox/314/ for more details.
@vloretz thank you so much and I shall take note of that. Does that mean
that my submission wouldn’t be revised and the patch wouldn’t be submitted
? Also, please let me know if I could be able to contribute to any other
hacks related to this hack.
Build is green
See https://jenkins.softwareheritage.org/job/DSTO/job/tox/319/ for more details.
.coverage.paris.28594.210279 | ||
---|---|---|
2 ↗ | (On Diff #4397) | For your information, those files (probably generated by tox or pytest) should not be committed. |