Ivan gingray

Why?

This:

.action {
  @extend .ml-3;
}

If you are getting this in gdb on macOS while trying to run a program:

Unable to find Mach task port for process-id 57573: (os/kern) failure (0x5).
 (please check gdb is codesigned - see taskgated(8))

Open Keychain Access
In menu, open Keychain Access > Certificate Assistant > Create a certificate
Give it a name (e.g. gdbc)

Finding a Ruby memory leak using a time analysis

When developing a program in Ruby, you may sometimes encounter a memory leak. For a while now, Ruby has a facility to gather information about what objects are laying around: ObjectSpace.

There are several approaches one can take to debug a leak. This discusses a time-based approach, where a full memory dump is generated every, say, 5 minutes, during a time that the memory leak is showing up. Afterwards, one can look at all the objects, and find out which ones are staying around, causing the

	### extract videos as mp3 files
	youtube-dl -x --audio-format mp3 <video link>

	### get highest resolution audio & video
	To download a video, you type the URL after the command like so:

	youtube-dl <video link>

	To select the video quality, first use the -F option to list the available formats, here’s an example,

	After automatically updating Postgres to 10.0 via Homebrew, the pg_ctl start command didn't work.
	The error was "The data directory was initialized by PostgreSQL version 9.6, which is not compatible with this version 10.0."

	Database files have to be updated before starting the server, here are the steps that had to be followed:

	# need to have both 9.6.x and latest 10.0 installed, and keep 10.0 as default
	brew unlink postgresql
	brew install [email protected]
	brew unlink [email protected]
	brew link postgresql

	DUMP
	// pod-name name of the postgres pod
	// postgres-user database user that is able to access the database
	// database-name name of the database
	kubectl exec [pod-name] -- bash -c "pg_dump -U [postgres-user] [database-name]" > database.sql

	RESTORE
	// pod-name name of the postgres pod
	// postgres-user database user that is able to access the database
	// database-name name of the database

	# Assumes the database container is named 'db'

	DOCKER_DB_NAME="$(docker-compose ps -q db)"
	DB_HOSTNAME=db
	DB_USER=postgres
	LOCAL_DUMP_PATH="path/to/local.dump"

	docker-compose up -d db
	docker exec -i "${DOCKER_DB_NAME}" pg_restore -C --clean --no-acl --no-owner -U "${DB_USER}" -d "${DB_HOSTNAME}" < "${LOCAL_DUMP_PATH}"
	docker-compose stop db

	SPC s c remove highlight

	**** Files manipulations key bindings
	Files manipulation commands (start with ~f~):

	\| Key Binding \| Description \|
	\|-------------+----------------------------------------------------------------\|
	\| ~SPC f c~ \| copy current file to a different location \|
	\| ~SPC f C d~ \| convert file from unix to dos encoding \|
	\| ~SPC f C u~ \| convert file from dos to unix encoding \|

	# for redirecting hhtp traffic to https version of the site
	server {
	listen 80;
	server_name example.com;
	return 301 https://$server_name$request_uri;
	}

	# for redirecting to non-www version of the site
	server {
	listen 80;

	package service

	var CalculateSum = calculateSum