Check your instance variable and methods names for conflicts with libraries or frameworks you are using if you get unexpected failures
Example 1: defining @response in your RSpec test setup when expecting to use the response from a HTTP request overwrites the result of the request. (don’t expect @request or @url to do you any favors either)
Example 2: Don’t define a #process method on a Rails controller
rake db:migrate db:seed ...) ruby classes do not get reloaded in between tasks so you can end up with old class definitions.
“Sean asked about git rebase complaining about no changes?”
The suggestion was that it was generally safe to just skip in this situation.
“Brent and Kris asked if anyone had encountered an after_destroy callback being called twice?”
Few suggestions were check that it was only one object being deleted, that there are no dependent objects being cascade deleted, etc.
“Joe asked about how to set default_url_options for? There are no mailers involved as far as he knew.”
Grant suggested trying to set it per class.
“New Lee asked about were there any updates/alternatives for AccessList as the gem is causing him grief with sorting.”
Ian knew of an alternative to AccessTree, Lee is still looking.
“Jonathan Berger asked if anyone has much experience with ShowOff?”
Davis was going to speak to Jonathan offline.
git push remote local:remote
“What’s the best admin gem out there?”
- I’ve used typus and it’s great, https://github.com/fesplugas/typus
- I know Erik Michaels-Ober has a good admin gem, https://github.com/sferik/rails_admin
- Active scaffold isn’t admin specific but that could work
“Amazon Web Services is down”
This is one of the longest outages we’ve seen of Amazon and thus Heroku. So many Ruby applications rely on Heroku that the community is certainly affected. Updates on the damage are on Heroku and Amazon. You can see how far reaching problems on EC2 are on ec2disabled.com
“Obama is in town!”
There have been rumors he is visiting a few notable software companies in the area, hopefully he’ll stop by. Watch out for blocked streets for the motorcade.
“How to diagnose a prolonged environment load?”
Boulder folks in town are experiencing a problem on a project where the Rails environment takes ~5 minutes to boot. They’ve timed the
requires
in their code and the delay seems to be after that. What’s a good way to approach this issue?
“solarized”
JPB passes along http://bit.ly/solarized-colors, a color scheme with some nice visual and ergonomic properties.
“respond_to :not_fun”
When using
respond_to
in a controller in Rails 3, keep in mind that the body of the action will still happen before it doesn’t find a
format
it is interested in and bails, possibly causing side effects of the action to still happen (like creating a record) but returning a 406 or other error to the client.
“Time.stub(:now) combined with waits”
Careful when stubbing
Time.now
when using, for example, steps in Cucumber that are “waiting” for things, as the clock will not move, and your tests will run until the end of time…