ralphtheninja

var test = require('tape');
var bytewise = require('bytewise');
var encode = bytewise.encode;
var MIN = bytewise.MIN;
var MAX = bytewise.MAX;

test('tuple queries', function (t) {
  var yearly = tuples('reports', 'yearly');

  // component keys of the tuple space query are available by index

ralphtheninja

MDB is unlike most debuggers you've experienced.

It is not a source level debugger like gdb or lldb or even Node's builtin debugger

Generally used for postmortem analysis.

Postmortem is for Production and Development

We operate mostly on core files, though you can attach to running processes as well.

ralphtheninja

initscript="
start on started networking
stop on stopping networking

respawn
env HOME='/root'

exec wiki -f -p 80
"

ralphtheninja

Interdisciplinary Open Source Community Conferences

Criteria

• Must be an event that someone involved in open source would be interested in attending
• Must be a community oriented event (no corporate owned for-profit events here please)
• Can't be about a specific language/framework.

Leave suggestions in the comments below

ralphtheninja

/**
 * Simple userland heapdump generator using v8-profiler
 * Usage: require('[path_to]/HeapDump').init('datadir')
 *
 * @module HeapDump
 * @type {exports}
 */

var fs = require('fs');
var profiler = require('v8-profiler');

ralphtheninja

bytespace-batchlog

Write-ahead logging for transactions in a bytespace.

Write operations are given a monotonically increasing id and written to transaction log. Batches are processed asynchronously and added to the store. By default, query methods withheld until batch processing is complete for the commit which was current at the time the query is received.

Batch processing pipeline

The batch processing pipeline exposes extensions points to allow pre-commit hooks to do additional work before committing to the transaction log, and post-commit hooks to do additional work after a transaction. Work can be isolated to specific subspaces, allowing heavyweight analytical processing to proceed without blocking queries in hot-path or transaction-heavy spaces. Analytical work can be delegated to subprocesses or even remote machines. Work on multiple commits can be batched together, and monotonically increasing batch ids can be leveraged to allow reads on possibly stale data to be held, e.g. until the next "

ralphtheninja

#!/bin/sh

git rebase --interactive --autosquash \
    $(git merge-base $(git symbolic-ref --short HEAD) master)

ralphtheninja

/*

create a simple source stream that reads from an array.

A pull stream is just an async stream that is called repeatedly.
note that when every item in the array has been called back,
it returns true in the error slot. This indicates the end of the stream.
both err and end mean the stream is over! but there are many possible
ways an error can occur (err && err !== true), and only one way a stream can correctly end (true)

ralphtheninja

#!/bin/bash
SERVER=yourwebsite.com
tar -cjf- ~/.crypt/passwd ~/.ssh ~/.bashrc ~/.profile ~/.vimrc ~/.gitconfig \
~/.config/chromium ~/.mozilla \
  | openssl enc -aes-256-cbc \
  | ssh $SERVER 'cat>~/www/backup/`date +%F.%T`'
ssh $SERVER 'ls -1 ~/www/backup | grep ^[0-9] | sort > ~/www/backup/list.txt'

ralphtheninja

{
  "name": "utp-hole-punching",
  "dependencies": {
    "utp-native": "*",
    "discovery-channel": "*"
  }
}