Bug 1190998 - zanata-client failed to push filename with plus sign (+) .
Summary: zanata-client failed to push filename with plus sign (+) .
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Zanata
Classification: Retired
Component: Component-zanata-client
Version: client-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Patrick Huang
QA Contact: Ding-Yi Chen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-10 08:26 UTC by Ding-Yi Chen
Modified: 2015-07-29 01:59 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-29 01:59:20 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1190979 0 unspecified CLOSED Error status 404 was returned when push documents with plus sign (+) in its parent directory 2021-02-22 00:41:40 UTC

Internal Links: 1190979

Description Ding-Yi Chen 2015-02-10 08:26:37 UTC
Description of problem:
When pushing GCC, which has libstdc++-v3/po/libstdc++.pot
zanata-client returned that this document is not found.

This file triggered both Bug 1190979 and this bug.
Bug 1190979 is about pushing directory with (+) and zanata-server returned 404
While this bug is about pushing filename with (+) and zanata-client returned "Document not found". So it may be from different defect.

Version-Release number of selected component (if applicable):
Client: zanatat-client-3.4.1
Server: Zanata 3.6.0-SNAPSHOT (git-server-3.5.1-152-g3b2474e)

How reproducible:
Always

Steps to Reproduce:
1. Download and extract GCC from ftp://mirror.aarnet.edu.au/pub/gnu/gcc/gcc-4.9.0.tar.gz
2. cd gcc-4.9.0
3. In Zanata server, create project gcc and version 4.9.0, and download zanata.xml
4. Rename directory libstdc++-v3/ to libstdc to avoid interfere from Bug 1190979:
   mv libstdc++-v3/po/libstdc++.pot libstdc++-v3/po/libstdc.pot
5. zanata-cli -B -e push --url $ZANATA_URL --username $ZANATA_USERNAME --key $ZANATA_KEY --from-doc "libstdc/po/libstdc++"

Actual results:
ERROR] Execution failed: 
java.lang.RuntimeException: Document with id libstd/po/libstdc++ not found, unable to start push from unknown document. Aborting.
        at org.zanata.client.commands.push.PushCommand.getDocsAfterFromDoc(PushCommand.java:487)
        at org.zanata.client.commands.push.PushCommand.pushCurrentModule(PushCommand.java:302)
        at org.zanata.client.commands.push.PushCommand.run(PushCommand.java:207)
        at org.zanata.client.commands.ConfigurableCommand.runWithActions(ConfigurableCommand.java:107)
        at org.zanata.client.commands.ArgsUtil.runCommand(ArgsUtil.java:48)
        at org.zanata.client.ZanataClient.processArgs(ZanataClient.java:170)
        at org.zanata.client.ZanataClient.main(ZanataClient.java:95)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
        at java.lang.reflect.Method.invoke(Method.java:620)
        at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
        at java.lang.Thread.run(Thread.java:863)


Expected results:
Push successfully

Additional info:

Comment 1 Zanata Migrator 2015-07-29 01:59:20 UTC
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-120


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