Bug 998294 - Multiple-part uploads fail hash check
Summary: Multiple-part uploads fail hash check
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Zanata
Classification: Retired
Component: ProjectType-Docs
Version: development
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: David Mason
QA Contact: Zanata-QA Mailling List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-19 01:36 UTC by David Mason
Modified: 2013-11-27 03:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-11-27 03:31:28 UTC
Embargoed:


Attachments (Terms of Use)

Description David Mason 2013-08-19 01:36:11 UTC
Description of problem:
Uploading in multiple chunks through the API using the Java clients or curl has started failing the hash check when the final part is uploaded. This appears to be because the last chunk is not being properly included when the chunks are combined to a complete file.


Version-Release number of selected component (if applicable):
3.0.2

How reproducible:
Always

Steps to Reproduce:
1. Create a project on Zanata, with project type 'file'
2. Download a config file for the project to a clean directory
3. Create a .txt file with contents "1234567890" in the directory
4. run the push command for source documents with option --chunk-size 3. e.g.
    zanata-cli push --push-type source --file-types txt -s . -t . --chunk-size 3

Actual results:
Upload fails due to hash mismatch.

Expected results:
Upload shows as successful on the client. Document is visible on the server with a single source string "1234567890"


Additional info:

Comment 1 Sean Flanigan 2013-08-19 02:32:08 UTC
Pull request: https://github.com/zanata/zanata-server/pull/133

Comment 3 Damian Jansen 2013-08-28 04:54:16 UTC
Verified at 6cffb1ba3ce14c4c5803c1e40556bd8d58a60363

Comment 4 Sean Flanigan 2013-11-27 03:31:28 UTC
Closing VERIFIED bugs which predate Zanata 3.1.2.


Note You need to log in before you can comment on or make changes to this bug.