bastman

Docker - How to cleanup (unused) resources

Once in a while, you may need to cleanup resources (containers, volumes, images, networks) ...

delete volumes

// see: https://github.com/chadoe/docker-cleanup-volumes

$ docker volume rm $(docker volume ls -qf dangling=true)

$ docker volume ls -qf dangling=true | xargs -r docker volume rm

ryanspradlin

type BatchLoadFn<K, V> = (keys: Array<K>) => Promise<Array<V | Error>>;

type LoadAllFn<K, V> = () => Promise<Array<[K, V]>>;

type Options<K, V> = {
  batch?: boolean,
  cache?: boolean,
  cacheMap?: CacheMap<K, Promise<V>>,
  cacheKeyFn?: (key: any) => any
};

michalkot

function weightedRandom(ar) {
	var ar = ar.sort(x => x.w);
	var sum = ar.reduce((p, c) => p + c.w, 0);
	// normalise
	var soFar = 0;
	ar.map(o => {
		o.w = o.w / sum;
		o.w += soFar;
		soFar += o.w;
	});

ctolsen

#!/usr/bin/env python3
import sys
import os


def curl_to_ab(curl_cmd: list, num: int=200, cur: int=4) -> str:
    """
    Translate a cURL command created by Chrome's developer tools into a
    command for ``ab``, the ApacheBench HTTP benchmarking tool.

jondlm

React introduced shallow rendering in 0.13. This is an excellent feature that I wish was included earlier in React. It aims to solve the problem of unit testing components without going through a real, or jsdom mocked, DOM. I couldn't find any info online about what lifecycle events it actually fires. So I did some testing of my own. To reproduce, put component.js and test.js into a folder and run node test.js.

TLDR; shallow rendering only invokes the following lifecycle hooks (in order):

1. getDefaultProps
2. getInitialState
3. componentWillMount stops here until re-render
4. componentWillReceiveProps
5. shouldComponentUpdate
6. componentWillUpdate

isaacsanders

This is a post by Joel Spolsky. The original post is linked at the bottom.

This is such a common question here and elsewhere that I will attempt to write the world's most canonical answer to this question. Hopefully in the future when someone on answers.onstartups asks how to split up the ownership of their new company, you can simply point to this answer.

The most important principle: Fairness, and the perception of fairness, is much more valuable than owning a large stake. Almost everything that can go wrong in a startup will go wrong, and one of the biggest things that can go wrong is huge, angry, shouting matches between the founders as to who worked harder, who owns more, whose idea was it anyway, etc. That is why I would always rather split a new company 50-50 with a friend than insist on owning 60% because "it was my idea," or because "I was more experienced" or anything else. Why? Because if I split the company 60-40, the company is going to fail when we argue ourselves to death. And if you ju

lightsofapollo

SlowDescribeReporter.prototype = {

    threshold: 400,

    reportRunnerStarting: function(runner){
        var i, len, suites = runner.suites_, self = this;
        this.topLevels = {};

        for(i = 0, len = suites.length; i < len; i++){
            (function(exec){