Open GoogleCodeExporter opened 8 years ago
[deleted comment]
I found the problem. For some reason is not accepting double quotes in the
"--source-snapshot", but accepted in other commands, for example, instance
name, disk name, snapshot name, ...
Original comment by thiag...@ciandt.com
on 6 Sep 2015 at 2:40
Thanks for the report. That should also have worked.
Did you run this command from command line or as part of a script (.bat or
.cmd) file.
Original comment by che...@google.com
on 8 Sep 2015 at 3:32
I ran in command line
Original comment by thiag...@ciandt.com
on 8 Sep 2015 at 3:37
Thanks, so the command you ran was
C:\my-path> gcloud compute disks create "thiagosb-hd-snap" "--source-snapshot"
"thiagosb-hd-snap1" --zone "us-central1-f"
Can you post stacktrace or error message you received? Thanks.
Original comment by che...@google.com
on 8 Sep 2015 at 4:20
Below the error, but add that this problem happens when it is done ctrl + v
command. If you enter, in command line, does not issue.
C:\Program Files\Google\Cloud SDK>gcloud compute disks create "thiagosb-hd-snap
" --source-snapshot "thiagosb-hd-snap1" --zone "us-central1-f"
Traceback (most recent call last):
File "C:\Program Files\Google\Cloud SDK\google-cloud-sdk\bin\..\./lib\googlecl
oudsdk\gcloud\gcloud.py", line 228, in main
_cli.Execute()
File "C:\Program Files\Google\Cloud SDK\google-cloud-sdk\bin\..\./lib\googlecl
oudsdk\calliope\cli.py", line 543, in Execute
raise exceptions.InvalidStringException(s_printable)
InvalidStringException: Failed to read command line argument ['\x93thiagosb-hd-s
nap\x94'] because it does not appear to be valid 7-bit ASCII. (Argument is comp
osed of bytes ["'\\x93thiagosb-hd-snap\\x94'"].)
Thanks you !!
Original comment by thiag...@ciandt.com
on 9 Sep 2015 at 11:51
Thanks, this is very useful.
What is happening is that when you copy/paste (depending on the source) quote "
character is sometimes represented as slanting ", which is understood very
differently by the tool from actual ".
This is common mistake, but it is not clear that we can do better job handling
such cases.
Original comment by che...@google.com
on 9 Sep 2015 at 5:54
[deleted comment]
I understand, but still does not make sense, because in other tools of this
command is handled properly as the contents of the clipboard.
In my opinion, the tool should show exactly how it will be processed, for
example, "'<name>'" instead of "<name>", helping the developer to identify
errors in the copy command.
Regardless, thanks for the clarification.
Original comment by thiag...@ciandt.com
on 9 Sep 2015 at 6:07
Thanks for the feedback. Will try to improve the error message for these cases.
Original comment by che...@google.com
on 10 Sep 2015 at 12:40
Original issue reported on code.google.com by
thiag...@ciandt.com
on 6 Sep 2015 at 2:33