Client reports 405 error when pushing files with no basename
Description
Description of problem:
the client reports what files are planning to be transferred on push though, if the target directory contains .pot say, it isn't included in the list but the operation simply failed like:
[INFO] pushing source doc [name= size=0] to server
[== ][ERROR] Operation failed: Error status 405 Method Not Allowed returned
To retry from the last document, please set the following option(s):
--from-doc ""
.
[ERROR] Execution failed: Error status 405 Method Not Allowed returned
If kinda "no name" is wrong, the client should ignore a dot file.
Version-Release number of selected component (if applicable):
Client version: 3.1.1
Client timestamp: 20130829-0208
API version: 3.0.1
API timestamp: 20130827-0636
Environment
Activity
Ding-Yi Chen commented:
What's the use case that ".pot" (without basename) are valid?
Akira TAGOH commented:
that was just a mistake in a script but assuming no human error is also wrong. at least the above navigation confuses to recover.
Ding-Yi Chen commented:
I can see the argument that client should return ERROR and stop for invalid document name, so you know something wrong.
However, for big project like man-page-l10n, users might be frustrated to see it stop on 90% just because of this.
We will put a warning message like:
[WARNING] Invalid filename: <dir>/.pot
Akira TAGOH commented:
That sounds good to me. thanks
Still exists in 4.0
Assignee
Reporter
Labels
Tested Version/s
Components
Sprint
Fix versions
Affects versions
Priority
