-
Delete all containers
$ docker ps -q -a | xargs docker rm
-q prints only the container IDs -a prints all containers
Notice that it uses xargs to issue a remove container command for each container ID
- Delete all untagged images
import AWS from 'aws-sdk'; | |
const lambda = new AWS.Lambda(); | |
const createAsyncInvokeParams = ( | |
{ | |
functionName, | |
payload | |
} | |
) => ({ |
#!/usr/bin/env node | |
const assert = require('assert'); | |
const { delay } = require('bluebird'); | |
const BigNumber = require('bignumber.js'); | |
const kraken = require('./kraken'); | |
const { | |
fetchMyOpenOrders, | |
fetchOrderBook, | |
placeOrder, |
Delete all containers
$ docker ps -q -a | xargs docker rm
-q prints only the container IDs -a prints all containers
Notice that it uses xargs to issue a remove container command for each container ID
// List all files in a directory in Node.js recursively in a synchronous fashion | |
var walkSync = function(dir, filelist) { | |
var fs = fs || require('fs'), | |
files = fs.readdirSync(dir); | |
filelist = filelist || []; | |
files.forEach(function(file) { | |
if (fs.statSync(dir + file).isDirectory()) { | |
filelist = walkSync(dir + file + '/', filelist); | |
} | |
else { |
The question: how can we use ES6 modules in Node.js, where modules-as-functions is very common? That is, given a future in which V8 supports ES6 modules:
export
syntax, without breaking consumers that do require("function-module")()
?import
syntax, while not demanding that the module author rewrites his code to ES6 export
?@wycats showed me a solution. It involves hooking into the loader API to do some rewriting, and using a distinguished name for the single export.
This is me eating crow for lots of false statements I've made all over Twitter today. Here it goes.
// Before April 2017 run this with flags: | |
// node --harmony-async-await ./async-test.js | |
function sayHi (name) { | |
if (name == null) throw Error('Missing name') | |
return `Hi ${name}.` | |
} | |
function sayWhatsUpAsync (msg, timeoutMs) { | |
console.log(`Will return in ${timeoutMs / 1000}s`) |
tim@touchsmart:~/Code$ nvm use v0.11.2-generators | |
Now using node v0.11.2-generators | |
tim@touchsmart:~/Code$ node --harmony testgen.js | |
<Buffer 76 61 72 20 66 73 20 3d 20 72 65 71 75 69 72 65 28 27 66 73 27 29 3b 0a 66 75 6e 63 74 69 6f 6e 20 72 65 61 64 46 69 6c 65 28 70 61 74 68 2c 20 65 6e 63 ...> | |
Sleeping for 2000ms... | |
Done |
// 🔥 Node 7.6 has async/await! Here is a quick run down on how async/await works | |
const axios = require('axios'); // promised based requests - like fetch() | |
function getCoffee() { | |
return new Promise(resolve => { | |
setTimeout(() => resolve('☕'), 2000); // it takes 2 seconds to make coffee | |
}); | |
} |
import "AssetLedger.sol"; | |
// TODO describe rules of exchange. | |
// In the AF market all users benefit from a "last look" facility to prevent | |
// them falling foul of mechanical arb sniping by those exploiting the way | |
// the blockchain and smart contract data lags the real markets being tracked. | |
// The system proceeds through a series of batching steps, which in practice | |
// might correspond to some number of blocks (for example, each batching step | |
// corresponds to a block). Orders collected in batching step B_i are initially | |
// in a "pending" state although visible within the book. Orders then remain |