sam-github

api_call.js: triggering a NodeReport via API call...

Writing Node.js report to file: NodeReport.20161101.085114.9593.001.txt
Node.js report completed
exception.js: throwing an uncaught user exception....

Writing Node.js report to file: NodeReport.20161101.085114.9599.001.txt
Node.js report completed
loop.js: going into loop now.... use kill -USR2 <pid> to trigger NodeReport
Uncaught #<UserException>

sam-github

api_call.js: triggering a NodeReport via API call...

Writing Node.js report to file: NodeReport.20161028.084405.30239.001.txt
Node.js report completed
loop.js: going into loop now.... use kill -USR2 <pid> to trigger NodeReport
fatalerror.js: allocating excessive javascript heap memory....
exception.js: throwing an uncaught user exception....

Writing Node.js report to file: NodeReport.20161028.084405.30245.001.txt
Node.js report completed

sam-github

// To cause warnings to be emitted, this needs to be run with:
//
//   NODE_EXTRA_CA_CERTS=x.pem
//
// and x.pem having invalid pem, perhaps a beginning of a cert without an end
// line, see below. My goal was to cause something to be printed between the
// BEGIN and END, no success.
//
// -----BEGIN CERTIFICATE-----
function log(s) {

sam-github

Unfortunately, they don't support our work flow... rebase and make a merge commit. sigh. the problem is they are
fighting and fighting from adding a couple of checkboxes and trying to just name workflows. squashing, rebasing,
and merge vs fast-forward are independent decisions, there are more possibilities than this weird UI can possibly
reflect.

When I'm github PM, I will make them do two settings for the repo:
- allow unrebased=yes/no (default yes)
- use-merge-commit=yes/no (default yes)

And then the PR merge button will have only two possibilities: squash=yes/no (default no)

sam-github

% npm view [email protected] .dependencies .optionalDependencies
.dependencies =  
{ compress: '^0.99.0',
  debug: '~0.7.4',
  ejs: '~2.3.4',
  lodash: '3.x.x',
  'node-uuid': '~1.4.3',
  optional: '^0.1.3',
  request: '>=2.9.0',

sam-github

Build for Scale

Who am I:

• email: [email protected]
• github: @sam-github
• twitter: @octetcloud

???

sam-github

63926f8 package: update to [email protected]
a798131 package: update license to use SPDX expression
33efe41 package: update strong-pm to ^1.5.x
6588613 package: update json-file-plus to avoid deprecated
d1e84de package: update README
57c86bd package: update jscs ignore rule
7d95107 package: update eslint to 0.17
4477cc1 package: update lodash to ^2.2
2fb8fa2 package: update dependencies to latest
e13760e package: update lint for CI

sam-github

'use strict';

var express = require('express');
var version = require('./package.json').version;

module.exports = function() {
  var app = express();

  app.get('/', function(req, res) {
    res.send('Hello World, v' + version);

sam-github

Keybase proof

I hereby claim:

• I am sam-github on github.
• I am octetcloud (https://keybase.io/octetcloud) on keybase.
• I have a public key whose fingerprint is 0034 A06D 9D9B 0064 CE8A DF6B F174 7F4A D230 6D93

To claim this, I am signing this object:

sam-github

{
    "env": {
        "browser": false,
        "node": true,
        "amd": false
    },

    "rules": {
        "no-alert": 2,
        "no-array-constructor": 2,