Call for testers. In addition to making sure that the scenarios described in Agile Web Development with Rails work with Rails 3.0, I’m monitoring the development on Rails 3.1. At the present time, I have a highly repeatable scenario that produces the error mentioned above (scroll to the bottom).
In order to test this, you need a current (master) clone of the following repositories:
If you have all three, I’d appreciate any help people can give in running the simple instructions mentioned in this bug, and reporting on the results you see in the bug report itself — either passes or failures. My plans are to try to reproduce this under a virtual machine, incrementally adding gems and packages to see if I can identify the environmental change which causes this failure.
OK, this makes no sense at all; but I created a virtual machine on one of the machines in which I had corruption problems, and initially the test passed. I then one by one installed packages until I saw the failure... and the packages which caused the problem was postfix.
I uninstalled postfix and the test passed again.
Tomorrow, I will destroy the virtual machine and reinstall fresh, and ONLY install what is needed to get the test to run, and then ONLY install postfix and see what happens.
cp -rp pre-corruption corrupt
sed -i s/rubys/$USER/ Gemfile
rake db:migrate db:seed
# once server has started, visit http://localhost:3000/ then:
# ... click on the first Add to Cart button; then Checkout; then Place Order
ruby ~/git/rails/bin/rails server
To verify that it was postfix that caused this:
sudo apt-get remove postfix
Note: both Rails master and Rails 3-0-stable use mail 2.2.12.