tahoe-lafs/trac-2024-07-25

useless error message when I use wrong syntax for a path in CLI commands, e.g. "tahoe cp" #1217

New issue

Open

opened 2010-10-01 18:20:47 +00:00 by zooko · 1 comment

zooko commented

2010-10-01 18:20:47 +00:00

Owner

I can never remember the syntax for putting caps directly on the command-line (not going through the "tahoe aliases" layer). Presumably I did something wrong here, but the error message sure isn't telling me what:

$ time tahoe cp --node-url=http://127.0.0.1:3456 ~/Movies/Miro/Sintel.2010.2K.Theora-VODO/Sintel.2010.2K.Theora-VODO.ogv 
URI:DIR2:77mdr6nhhzqo22lvviojxbqooy:dkkrzum2rynr2sxunwn5n7arusmuxw3m27k3f4yo2t67rqzz6xia:Sintel.2010.2K.Theora-VODO.ogv
Error during PUT: 501 Not Implemented
"I don't know how to treat a PUT request."

real    0m49.419s
user    0m1.998s
sys     0m2.653s

I can never remember the syntax for putting caps directly on the command-line (not going through the "tahoe aliases" layer). Presumably I did something wrong here, but the error message sure isn't telling me what: ``` $ time tahoe cp --node-url=http://127.0.0.1:3456 ~/Movies/Miro/Sintel.2010.2K.Theora-VODO/Sintel.2010.2K.Theora-VODO.ogv URI:DIR2:77mdr6nhhzqo22lvviojxbqooy:dkkrzum2rynr2sxunwn5n7arusmuxw3m27k3f4yo2t67rqzz6xia:Sintel.2010.2K.Theora-VODO.ogv Error during PUT: 501 Not Implemented "I don't know how to treat a PUT request." real 0m49.419s user 0m1.998s sys 0m2.653s ```

tahoe-lafs added the

code-frontend-cli

labels 2010-10-01 18:20:47 +00:00

tahoe-lafs added this to the undecided milestone 2010-10-01 18:20:47 +00:00

davidsarah commented

2011-08-03 22:03:16 +00:00

Author

Owner

#1379 (another case of a poor error message due to wrong path syntax) has been closed as a duplicate of this ticket. The fix should work for all path arguments to any CLI command.

As in #1379, the problem here is that $CAP:$PATH was used instead of $CAP/$PATH.

#1379 (another case of a poor error message due to wrong path syntax) has been closed as a duplicate of this ticket. The fix should work for all path arguments to any CLI command. As in #1379, the problem here is that $CAP:$PATH was used instead of $CAP/$PATH.

tahoe-lafs modified the milestone from undecided to 1.10.0

2011-08-03 22:03:16 +00:00

tahoe-lafs changed title from ~~useless error message when I use wrong syntax for a cap in "tahoe cp"~~ to useless error message when I use wrong syntax for a path in CLI commands, e.g. "tahoe cp"

2011-08-03 22:03:16 +00:00

Sign in to join this conversation.

No labels

LeastAuthority.com automation

cannot reproduce

code-frontend-cli

code-frontend-ftp-sftp

code-frontend-magic-folder

code-frontend-web

code-peerselection

dev-infrastructure

somebody else's problem

was already fixed

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#1217

No description provided.