tilthouse

Keybase proof

I hereby claim:

• I am tilthouse on github.
• I am tilthouse (https://keybase.io/tilthouse) on keybase.
• I have a public key ASA8nvVZPbUCw7TF4Pl6nXoiphk8LnR1HBNC-GnnHyv7fgo

To claim this, I am signing this object:

tilthouse

Homebrew build logs for gcc@4.9 on macOS 10.14
Build date: 2018-09-25 14:24:01

tilthouse

Homebrew build logs for gcc@4.9 on macOS 10.14
Build date: 2018-09-25 09:31:39

tilthouse

I implemented this as a gem which can be found at https://github.com/tilthouse/scf_exercise For much higher performance, there exist native gems, We could also use the 'job_interview' gem: https://github.com/ruby-jokes/job_interview

FWIW, this seemed familiar. Turns out I did this problem from Project Euler in 2012. I did not create a gem for it at that time. My "get the answer quickly" solution from the time is at https://github.com/tilthouse/project_euler/blob/master/problems/002/answer002.rb I did look this up after doing this exercise again. My previous solution did not use caching, for example.

tilthouse

ActiveRecord::StatementInvalid in ProductsController#index

PGError: ERROR:  relation "pages" does not exist
LINE 4:              WHERE a.attrelid = '"pages"'::regclass
                                        ^
:             SELECT a.attname, format_type(a.atttypid, a.atttypmod), d.adsrc, a.attnotnull
              FROM pg_attribute a LEFT JOIN pg_attrdef d
                ON a.attrelid = d.adrelid AND a.attnum = d.adnum
             WHERE a.attrelid = '"pages"'::regclass
               AND a.attnum > 0 AND NOT a.attisdropped

tilthouse

Your OS X is ripe for brewing.
Any troubles you may be experiencing are likely purely psychosomatic.

tilthouse

$ cap -vv staging deploy
  * executing `staging'
  * executing `multistage:ensure'
  * executing `deploy'
  * executing `deploy:update'
 ** transaction: start
  * executing `deploy:update_code'
  * executing "if [ -d /var/www/onlineapp/staging/shared/cached-copy ]; then cd /var/www/onlineapp/staging/shared/cached-copy && git fetch -q origin && git reset -q --hard f01e070901b274fcb1024bc4a5f7f383eb1f07b8 && git submodule -q init && for mod in `git submodule status | awk '{ print $2 }'`; do git config -f .git/config submodule.${mod}.url `git config -f .gitmodules --get submodule.${mod}.url` && echo Synced $mod; done && git submodule -q sync && git submodule -q update && git clean -q -d -x -f; else git clone -q git@github.com:dzap/dingus.git /var/www/onlineapp/staging/shared/cached-copy && cd /var/www/onlineapp/staging/shared/cached-copy && git checkout -q -b deploy f01e070901b274fcb1024bc4a5f7f383eb1f07b8 && git submodule -q init && git submodule -q sync && git submodule -q update --recursive; fi"
 ** [dingus-s