~/talk

Dissecting Ruby with Ruby

Talkat RailsConf 2013 · 2013-04-29..05-02· [ruby, testing]
slides:none on file

Uses nothing fancy beyond prints and kernel probes to find the exact ruby file and line that a method comes from and where it was called, demonstrating caller.inspect, Method#source_location and Module methods like instance_method. Applied to Rails actionpack url_for/link_to confusion caused by a host set to "http://", traced the stack, added a protocol‑stripping change, tests and changelog, and turns that diagnosis into a pull request that lands in Rails.

AI-written summary · about

  1. 0:00Start
  2. 0:38married to Ruby, so to speak
  3. 7:36Let's look at Ruby
  4. 8:04Kernel#caller gives you the back trace
  5. 11:19link_to in (rails) email templates needs a host set, but fails if you include http
  6. 14:08Method# source_location to the rescue
  7. 15:59Too much Ruby?
  8. 17:17What were we doing?
  9. 20:30Reproduce the problem
  10. 21:02Awareness (open an issue)
  11. 22:42Any other fun features?
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.