vcs import fails when credentials are needed about vcstool HOT 8 CLOSED

I added docs about the --workers option and its effect on stdin processing: #119.

So maybe one has to stop the execution of additional workers if subprocess.communicate in VcsClientBase

While executing all the commands sequentially that would also mostly prohibit the performance improvements achieved by multiple workers. So I don't see it being a viable alternative to --workers 1. Unfortunately I don't have a suggestion for you.

from vcstool.

vcstool is currently not designed to provide stdin to any of the commands executed. Simply because I don't have a use case for this.

I am not sure how much effort it would be to implement support for user input. I would be happy to review a pull request for this.

from vcstool.

Understood. Good to know this is expected behavior.

It is certainly not an easy problem. Just piping stdin in from the user wouldn't be exceptionally useful because you would still have to enter credentials for each repo every time.

For now I'll just change the way I authenticate on remotes.

from vcstool.

I will mark this as "wontfix" since I don't intend to work on this. If someone can come up with a pull request implementing this somehow I would be more than happy to review and integrate it.

from vcstool.

would be nice to have that feature

from vcstool.

would be nice to have that feature

Please feel free to contribute a pull request.

from vcstool.

Do you have recommendations where to start?

from vcstool.

hotfix is to set number of workers to 1, e.g.

vcs import < yaml_file.repos --workers=1

So maybe one has to stop the execution of additional workers if subprocess.communicate in VcsClientBase

from vcstool.