Skip to content

Instantly share code, notes, and snippets.

On vacation

Oshan Wisumperuma oshanz

On vacation
View GitHub Profile
View Using GDB to inspect a running Ruby

That’s not a great thing to have to say, is it? However, I bet you’ve said it before and may not have immediately know why.

With liberal use of puts and maybe pry, you can figure out what a problem might be next time you run it, but sometimes you need to figure out what that problem is right now.

As it turns out, and I know this is a shocker, Ruby processes are just regular processes. They can be debugged with gdb.

Having recently had the need to find out why a job of mine was running particularly slowly, I found out about this lovely tool the hard way: frantic googling. I found some very useful functions for gdb in a blog post by Rasmus on Ruby callstacks.

View gist:0cf81ffecc5893e07527e92c4518555d
curl -GET "http://localhost:9200/_cluster/allocation/explain?pretty"
curl -XPOST 'localhost:9200/_cluster/reroute?retry_failed'
View questions
- What are you hoping I’ll change?
- How does your development process work?
- What tools does your team use to communicate?
- what happened to last person?
- If I’m not meeting expectations, how will I know?
- How will I get better at my job?
* The [Vega ecosystem](
  * [Altair]( - declarative data visualization
  * [Voyager]( - Automatic Exploratory Data Analysis
  * [Lyra]( - Tableau-like data visualization design
* [Seaborn](
* [](
oshanz /
Created Apr 23, 2020
tune postgraphile

npx postgraphile -c my_db_name -s my_schema_name

postgraphile --disable-query-log --simple-collections only --disable-graphiql --legacy-relations omit --no-setof-functions-contain-nulls --max-pool-size 20

You can’t perform that action at this time.