importing using ssh with version key specified leads to ValueError
See original GitHub issueInvocation of command 'import' on client 'git' failed: ValueError: need more than 1 value to unpack (/usr/lib/python2.7/dist-packages/vcstool/clients/git.py:477)
Line in question is
hash_, ref = line.split(None, 1)
public repos imported using https and version seem to import correctly, but importing repos with ssh and version is leading me to the error. Importing repos with ssh and no version seems to work correctly.
vcs version: 0.2.10 python version: 2.7.12
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
New to Python and Paramiko. Getting ValueError("q must be ...
Hello, so I'm trying to ssh into my work server, and I keep getting the above error.
Read more >paramiko: why cannot use explicitly specified key?
The key is encoded using rsa-sha2-512 . Finally, when I move the key from ~/.ssh, and clear the auth cache, I can no...
Read more >connection — Fabric documentation
ValueError – if user or port values are given via both host shorthand and their own arguments. (We refuse the temptation to guess)....
Read more >Connecting | Elasticsearch Python Client [master] | Elastic
When connecting to Elastic Cloud with the Python Elasticsearch client you should always use the cloud_id parameter to connect.
Read more >Key Serialization — Cryptography 3.4.2 documentation
ValueError – If the PEM data could not be decrypted or if its structure could not be decoded successfully. TypeError – If a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The fix works!
In our case, each line of the banner does not start with ‘#’, and looks like what I posted above, with literally a line of
-----------------
on top and below of a lot of text describing security and privacy agreements, which also means for our case, the statement to catch ‘#’ does nothing, but the problem is still solved by the try except. (I can vcs import even when I delete the lines to catch if it starts with ‘#’)I believe in general, these banners can be whatever the system administrators want them to be, so I’m not sure if there is a clear pattern to distinguish them.
Thanks for helping debug this and checking the patch. This will be addressed in the upcoming patch release.