danrigsby

packer build packer.json 2>&1 | sudo tee output.txt
tail -2 output.txt | head -2 | awk 'match($0, /ami-.*/) { print substr($0, RSTART, RLENGTH) }' > sudo ami.txt

cryptix

package main

import (
	"io"
	"log"
	"mime/multipart"
	"net/http"
	"os"
	"path/filepath"
	"runtime"

Seldaek

// Run this in web console

var rows = $('table tr').get();
rows.sort(function(a, b) {
  var keyA = $(a).find('img[src="/lib/images/success.png"]').attr('title') || '0';
  var keyB = $(b).find('img[src="/lib/images/success.png"]').attr('title') || '0';
  if (keyA < keyB) return -1; if (keyA > keyB) return 1; return 0;
});
$.each(rows, function(index, row) {$('table tbody').append(row);});

auroraeosrose

1. Interfaces for streams wrappers (clean up apis) - primarily userland, small to no BC
2. Resources -> objects (engine storage and attachment) - primarily core, some BC issues
3. finish implementations for callbacks - primarily feature addition
4. async IO features (see: jpauli) - feature addition with core implications and some BC issues
5. curl:// stream wrapper - feature addition (functionality of --with-curl-wrappers but with curl:// as prefix)
6. filtering api - buckets hard to use, user_filter class is api possessed - userland and BC
7. factory registration for wrapper creation - feature addition
8. ability to plug into transports from php land instead of requiring C extensions

Streams Interfaces:

irgeek

Finding Packer-generated AMIs automatically after builds

The basic technique is to have Packer add a tag with a unique value during the build, and use AWS' built-in filtering capabilities to find that specific AMI after the build finishes.

• template.json - Shows the settings that need to be added to your template
• build.sh - Shows how to use the template to do a build and retrieve the AMI information

isaacs

# Hello, and welcome to makefile basics.
#
# You will learn why `make` is so great, and why, despite its "weird" syntax,
# it is actually a highly expressive, efficient, and powerful way to build
# programs.
#
# Once you're done here, go to
# http://www.gnu.org/software/make/manual/make.html
# to learn SOOOO much more.

doctorallen

#!/usr/bin/env bash 
# You will want to also add the git today command: https://github.com/doctorallen/dotfiles/blob/master/.gitconfig#L49                                                                                                                                                                                                                       

root=$1
if [ -n "$root"]         
    then
        echo "Error: please define the root directory location for your report."
        read root    
fi
lastchar=${#root}-1

lavalamp

There are three easy to make mistakes in go. I present them here in the way they are often found in the wild, not in the way that is easiest to understand.

All three of these mistakes have been made in Kubernetes code, getting past code review at least once each that I know of.

1. Loop variables are scoped outside the loop.

What do these lines do? Make predictions and then scroll down.

func print(pi *int) { fmt.Println(*pi) }

ksimka

<?php

$a = [];
//$s = 123456;
$s = 's6tbdfgj222dJGk';
$rs = str_repeat("0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ", 10);

$numGen = function() {
    return rand(1, 9999999);
};

mcos

package main

import (
	"crypto/rand"
	"fmt"
)

func randStr(strSize int) string {
	dictionary := "0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz"