eeb750cd33
Here we implement a naive solution to #5605 which catches the case that a provided source contains an object which cannot be inspected, because an object contained within in has an #inspect string that returns a string that is incompatible with the encoding in `Encoding.default_external` or a string which cannot be downcast to 7-bit ascii. The Ruby VM implementation of "#inspect" implements this checking on these lines of code: http://git.io/vZYNS. A Ruby level override of this method does not cause this problem. For example: ```ruby class Foo def inspect "😍".encode("UTF-16LE") end ``` will not cause the problem, because that's a Ruby implementation and the VM's checks don't occur. However, if we have an Object which **does** use the VM implementation of inspect, that contains an object that has an inspect string which returns non-ascii, we encounter the bug. For example: ```ruby class Bar def inspect "😍".encode("UTF-16LE") end end class Foo def initialize @bar = Bar.new end end Foo.new.inspect ``` Will cause the issue. The solution this patch provides basically catches the encoding error and inserts a string which attempts to help the user work out which object was provided without blowing up. Most likely, this was caused by a user having a weird encoding coming out of one of the sources passed in, but without a full repro case, it's not clear whether a patch should be applied to a different object in the system. Closes #5605.
Vagrant
- Website: http://www.vagrantup.com
- Source: https://github.com/mitchellh/vagrant
- IRC:
#vagranton Freenode - Mailing list: Google Groups
Vagrant is a tool for building and distributing development environments.
Development environments managed by Vagrant can run on local virtualized platforms such as VirtualBox or VMware, in the cloud via AWS or OpenStack, or in containers such as with Docker or raw LXC.
Vagrant provides the framework and configuration format to create and manage complete portable development environments. These development environments can live on your computer or in the cloud, and are portable between Windows, Mac OS X, and Linux.
Quick Start
For the quick-start, we'll bring up a development machine on VirtualBox because it is free and works on all major platforms. Vagrant can, however, work with almost any system such as OpenStack, VMware, Docker, etc.
First, make sure your development machine has VirtualBox installed. After this, download and install the appropriate Vagrant package for your OS.
To build your first virtual environment:
vagrant init hashicorp/precise32
vagrant up
Note: The above vagrant up command will also trigger Vagrant to download the
precise32 box via the specified URL. Vagrant only does this if it detects that
the box doesn't already exist on your system.
Getting Started Guide
To learn how to build a fully functional development environment, follow the getting started guide.
Installing the Gem from Git
If you want the bleeding edge version of Vagrant, we try to keep master pretty stable and you're welcome to give it a shot. The following is an example showing how to do this:
rake install
Ruby 2.0 is needed.
Contributing to Vagrant
Dependencies and Unit Tests
To hack on Vagrant, you'll need bundler which can
be installed with a simple gem install bundler. Afterwards, do the following:
bundle install
rake
This will run the unit test suite, which should come back all green! Then you're good to go!
If you want to run Vagrant without having to install the gem, you may use bundle exec,
like so:
bundle exec vagrant help
NOTE: By default running Vagrant via bundle will disable plugins.
This is necessary because Vagrant creates its own private Bundler context
(it does not respect your Gemfile), because it uses Bundler to manage plugin
dependencies.
Acceptance Tests
Vagrant also comes with an acceptance test suite that does black-box tests of various Vagrant components. Note that these tests are extremely slow because actual VMs are spun up and down. The full test suite can take hours. Instead, try to run focused component tests.
To run the acceptance test suite, first copy vagrant-spec.config.example.rb
to vagrant-spec.config.rb and modify it to valid values. The places you
should fill in are clearly marked.
Next, see the components that can be tested:
$ rake acceptance:components
cli
provider/virtualbox/basic
...
Then, run one of those components:
$ rake acceptance:run COMPONENTS="cli"
...