You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 28, 2023. It is now read-only.
Hopefully this will be fixed in newer versions of Vagrant, but as of 1.6.1, the provisioner logs every write to stdout/stderr on a new line, even if a program was printing a line (like a progress bar) character-by-character. This looks especially bad for wget because it defaults to the "dot" progressbar when connected to a non-TTY and prints a "." for each 1K downloaded. This will overwhelm many people's scrollback and it's a good idea to always review the entire provision log.
Hopefully this will be fixed in newer versions of Vagrant, but as of 1.6.1, the provisioner logs every write to stdout/stderr on a new line, even if a program was printing a line (like a progress bar) character-by-character. This looks especially bad for wget because it defaults to the "dot" progressbar when connected to a non-TTY and prints a "." for each 1K downloaded. This will overwhelm many people's scrollback and it's a good idea to always review the entire provision log.
If you want to work around it for now, use the change in https://github.com/railsbridge-boston/railsbridge-vm/compare/wgetrc . This just makes the dots represent 1M instead of 1K, so there are fewer of them.
In the meantime, remember to use
curl -s
.The text was updated successfully, but these errors were encountered: