Debugging Rails Itself
summary
Explains the exact process to fix a bug in Rails from report to committed patch: create a reproducible single-file test (only Rails plus sqlite/pg), use git bisect (about seven steps) to find the offending commit, inspect code paths with prints, pry or the p-method, and use git context instead of blame to see intent. Shows when a behavior is a bug (differs from docs/public API), how to find the introducing commit, and how to avoid regressing prior fixes.
AI-written summary · about
chapters (33)
- 0:00Intro
- 0:55Who am I
- 1:14Meet Ruby
- 1:34Anybody can work on Rails
- 2:00Its not scary
- 2:19Techniques
- 2:32What is a bug
- 3:14At least surprise
- 3:42Not supported usage
- 6:24Reproducible Test Case
- 6:39Active Record
- 7:21Minimal Isolated Environment
- 7:56The Test
- 9:44What Next
- 10:12Bug on Table
- 10:36bisect
- 11:47bisecting
- 12:46contribute
- 13:13thanks a lot
- 13:30bug report
- 13:54legacy code
- 14:34method method
- 15:50other methods
- 17:35callbacks
- 19:13inspect
- 19:26getblame
- 19:52recontext
- 23:41go home
- 23:54find a pair
- 24:17anyone can work on Rails
- 24:34my wife is giving a talk
- 24:51thank you Shopify
- 25:14Ruby Stickers
related talks
37mPrying Open The Black Box
39mPerusing the Rails Source Code - A Beginners Guide
28mTeaching RSpec to Play nice with Rails
35mMerged PRs: An Untapped Resource for Practice and Exploration
37mDon't touch that!
34mCode Spelunking: teach yourself how Rails works
41mRuby on Rails Hacking Guide
29mYes, You Can Work on Rails & any other Gem