Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

stops running when one of the vagrantfiles has an error #6

Open
zakariaboualaid opened this issue Jun 4, 2017 · 0 comments
Open

stops running when one of the vagrantfiles has an error #6

zakariaboualaid opened this issue Jun 4, 2017 · 0 comments

Comments

@zakariaboualaid
Copy link

zakariaboualaid commented Jun 4, 2017 •
edited
Loading

I have a project with more than 10 Vagrantfiles and one of them got a specific ruby error.
I noticed that vscode-vagrant stops running when encountering an error in at least one of the Vagrantfiles. Until running using debug mode, the error can be noticed, however as a normal user, vscode-vagrant does nothing.

Example of an error
jenkins/Vagrantfile:5:in read: No such file or directory .vagrant_key_id (Errno::ENOENT)
@zakariaboualaid zakariaboualaid mentioned this issue Jun 4, 2017
Open
@zakariaboualaid zakariaboualaid changed the title When one Vagrantfile throw an error, vscode-vagrant stops running for the other ones and does nothing stops running when one of the vagrantfiles has an error Jun 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@zakariaboualaid