jhorikawa

float sigma = chf("sigma");
int res = chi("res");
int resx = chi("resx");
int resy = chi("resy");
int resn = floor(res / 2.0);
float weightTotal = 0;
float valTotal = 0;
for(int i=-resn; i<=resn; i++){
    for(int n=-resn; n<=resn; n++){
        float ix = @ptnum % resx + i;

sneha-belkhale

float hash (float2 n)
{
    return frac(sin(dot(n, float2(123.456789, 987.654321))) * 54321.9876 );
}

float noise(float2 p)
{
    float2 i = floor(p);
    float2 u = smoothstep(0.0, 1.0, frac(p));
    float a = hash(i + float2(0,0));

crucialfelix

/**
 *  analytics.js;
 * Copyright 2019 Chris Sattinger
 * MIT license - do as thou wilt
 * 
 * This will send page views on route change to Google Analytics.
 * Works with https://nextjs.org/ and https://github.com/fridays/next-routes
 **/

import Router from "next/router";

kaihendry

# Full text search

[hendry@t480s 5xx]$ cat bugzilla.sh
aws --profile uneet-dev logs filter-log-events --log-group-name bugzilla --start-time $(date -d "-1 hour" +%s000) \
        --filter-pattern '"apex/ping/v1.0"'
        
# (faster) Query on a JSON structured log
        
[hendry@t480s 5xx]$ cat alambda.sh
aws --profile uneet-demo logs filter-log-events --log-group-name "/aws/lambda/alambda_simple" --start-time $(date -d "-8

peerreynders

defmodule FromPipe do
  #
  # Use a helper script "from_pipe_release" to
  # release/request each line read from the
  # named pipe - effectively implementing a
  # crude backpressure mechanism
  #
  @pipe_name "/tmp/testpipe"
  @from_pipe_release "./from_pipe_release"
  @from_pipe_clean "./from_pipe_clean"

krisleech

Renew GPG key

Given that your key has expired.

$ gpg --list-keys
$ gpg --edit-key KEYID

Use the expire command to set a new expire date:

jlis

image: docker:latest

variables:
  REPOSITORY_URL: <AWS ACCOUNT ID>.dkr.ecr.eu-central-1.amazonaws.com/<ECS REPOSITORY NAME>
  REGION: eu-central-1
  TASK_DEFINTION_NAME: <TASK DEFINITION NAME>
  CLUSTER_NAME: <CLUSTER NAME>
  SERVICE_NAME: <SERVICE NAME>

services:

shortjared

a4b.amazonaws.com
access-analyzer.amazonaws.com
account.amazonaws.com
acm-pca.amazonaws.com
acm.amazonaws.com
airflow-env.amazonaws.com
airflow.amazonaws.com
alexa-appkit.amazon.com
alexa-connectedhome.amazon.com
amazonmq.amazonaws.com

subfuzion

Overview

This gist is based on the information available at golang/dep, only slightly more terse and annotated with a few notes and links primarily for my own personal benefit. It's public in case this information is helpful to anyone else as well.

I initially advocated Glide for my team and then, more recently, vndr. I've also taken the approach of exerting direct control over what goes into vendor/ in my Dockerfiles, and also work from isolated GOPATH environments on my system per project to ensure that dependencies are explicitly found under vendor/.

At the end of the day, vendoring (and committing vendor/) is about being in control of your dependencies and being able to achieve reproducible builds. While you can achieve this manually, things that are nice to have in a vendoring tool include:

mwgkgk

tl;dr:

$ iex --sname server
$ iex --sname client
iex(client@localhost)> Node.connect :"server@localhost"

Start a named node:

$ iex --name any_name@any_domain