schacon

#!/bin/bash

# Colors
RED='\033[0;31m'
GREEN='\033[0;32m'
NO_COLOR='\033[0m'
BLUE='\033[0;34m'
YELLOW='\033[0;33m'
NO_COLOR='\033[0m'

schacon

require 'rugged'

# Your specified file is the first argument
file_path = ARGV[0]

repo = Rugged::Repository.discover(File.dirname(file_path))
walker = Rugged::Walker.new(repo)
walker.push(repo.head.target.oid)
walker.sorting(Rugged::SORT_TOPO)

schacon

// first, grab a list of the field names in a table

SELECT STRING_AGG(column_name, ", \n" ORDER BY ordinal_position)
FROM [project_name].[dataset_name].INFORMATION_SCHEMA.COLUMNS
where table_name = 'blah'
group by table_name

schacon

version: '3'
services:
  app:
    build:
      context: ..
      dockerfile: .devcontainer/Dockerfile
      args:
        VARIANT: 2.6
        NODE_VERSION: "lts/*"
    volumes:

schacon

select month, months_out from (
    select month,
        GENERATE_ARRAY(0, DATE_DIFF(CURRENT_DATE(), month, MONTH)) as months,
    from UNNEST(
        (select 
            GENERATE_DATE_ARRAY(CAST([STARTING_DATE] AS DATE), CAST(max(date_field) AS DATE), 
                INTERVAL 1 MONTH) as date
        from [SOME_TABLE_WITH_A_DATE_FIELD])
    ) as month
) CROSS JOIN UNNEST(months) as months_out

schacon

Keybase proof

I hereby claim:

• I am schacon on github.
• I am scottchacon (https://keybase.io/scottchacon) on keybase.
• I have a public key ASAcTJsFnTw59Ncpg1Bax0VQ1yH1B3N2MQaDHsadrT95aAo

To claim this, I am signing this object:

schacon

#! /usr/bin/env ruby
require 'rubygems'
require 'oily_png'

Dir.glob("book/**/*.png").each do |file|
  puts file
  image = ChunkyPNG::Image.from_file(file)
  p image.width
  p image.height
  if image.width > 800 || image.height > 800

schacon

// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console

schacon

dfg

schacon

HTTP transfer protocols
=======================

Git supports two HTTP based transfer protocols.  A "dumb" protocol
which requires only a standard HTTP server on the server end of the
connection, and a "smart" protocol which requires a Git aware CGI
(or server module).  This document describes both protocols.

As a design feature smart clients can automatically upgrade "dumb"
protocol URLs to smart URLs.  This permits all users to have the