Skip to content
This repository has been archived by the owner on Sep 19, 2021. It is now read-only.

Winpty update, PATH and insecure wget fix #34

Merged
merged 1 commit into from
Apr 27, 2018

Conversation

murray02
Copy link

Update winpty Version to 0.4.3.

Update wget to make the request for machines that do not have insecure wget enabled. This is also made silent to keep the prompt clean. It would also explain why people were having issues when doing babun-docker-update and not seeing errors.

Prepending the PATH helped with finding the exe for winpty.

…hat do not have insecure wget enabled. This is also made silent to keep the prompt clean. Prepending the PATH helped with finding the exe for winpty.
@murray02
Copy link
Author

PING!

@tiangolo
Copy link
Owner

Thanks for your work!

Prepending the PATH helped with finding the exe for winpty.

Can you explain how this would help?

@murray02
Copy link
Author

I am not 100% on this but with my business machine, I think this is an issue with PATH length. Windows does have limitations.

https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx

Mine is extremely long so I think that Babun is ignoring after the 260 char limit.

@tiangolo tiangolo merged commit cc8d824 into tiangolo:master Apr 27, 2018
@tiangolo
Copy link
Owner

Good point. Thanks for the link and for your work! 🎉

@tiangolo tiangolo mentioned this pull request Apr 27, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants