Summary of the Node.js Board controversy from what I can gather.
All the redactions (and hidden/private conversations) has made it very hard for the outside to figure out what has occured.
Node.js Community Committee wanted Rod out:
addEventListener('fetch', event => { | |
event.respondWith(handleRequest(event)) | |
}) | |
/** | |
* Entry point of the worker | |
*/ | |
async function handleRequest(event) { | |
try { | |
// Get the JWT |
# These filters are based on email that Tim Hockin sent to kubernetes-dev a | |
# while ago on how to bring some sanity to github notifications with Kubernetes. | |
# | |
# https://groups.google.com/forum/#!msg/kubernetes-dev/5qU8irU7_tE/aZov0LpCBwAJ | |
# | |
# This file can be processed with https://github.com/mesozoic/gmail-yaml-filters | |
# Mark all k8s email | |
- match: | |
any: |
const Page = require('puppeteer/lib/Page'); | |
// the following 2 methods are originally from: https://github.com/GoogleChrome/puppeteer/issues/85#issuecomment-341743259, with some modification to fit puppeteerv1.0.0 | |
async function newPageWithNewContext(browser) { | |
const { browserContextId } = await browser._connection.send('Target.createBrowserContext'); | |
const { targetId } = await browser._connection.send('Target.createTarget', { url: 'about:blank', browserContextId }); | |
const target = await browser._targets.get(targetId); | |
const client = await browser._connection.createSession(targetId); | |
const page = await Page.create(client, target, browser._ignoreHTTPSErrors, browser._appMode, browser._screenshotTaskQueue); | |
page.browserContextId = browserContextId; |
package main | |
import ( | |
"context" | |
"flag" | |
"fmt" | |
"log" | |
"net/http" | |
"os" | |
"os/signal" |
### Removes Node and NPM from mac OS ### | |
# Uninstall using NPM | |
npm uninstall npm -g || echo "NPM uninstall didn't work" | |
# Try if Node's installed with Brew | |
(brew uninstall node&&brew prune)||echo "Node was not installed with Brew" | |
# Remove all files and folders including Node or NPM | |
rm -rf /usr/local/{lib/node{,/.npm,_modules},bin,share/man}/{npm*,node*,man1/node*} | |
rm -rf /usr/local/bin/npm /usr/local/share/man/man1/node* /usr/local/lib/dtrace/node.d ~/.npm ~/.node-gyp /opt/local/bin/node opt/local/include/node /opt/local/lib/node_modules | |
rm -rf /usr/local/{lib/node{,/.npm,_modules},bin,share/man}/npm* | |
rm -rf /usr/local/include/node* |
# I had a bit of trouble getting my unifi controller (hosted offsite) to use a proxy/letsencrypt. So here are the fruits of my labor. | |
# The unifi default port is 8443 running on localhost. | |
# License: CC0 (Public Domain) | |
server { | |
# SSL configuration | |
# | |
listen 443 ssl default_server; | |
listen [::]:443 ssl default_server; |
# Let's add a few entries in our stream "mystream". Every entry in a stream is like | |
# an hash, composed of fields and values, but every entry can have different fields. | |
# XADD appends a new entry in a stream, and returns an unique ID which is guaranteed | |
# be incrementing. | |
# The first part of the ID is the millisecond unixtime during the | |
# addition (or the time of the last entry in the stream, if greater than the current time). | |
# The second part of an entry is a 64 bit counter for entries added in the same ms. | |
127.0.0.1:6379> XADD mystream name pamela nicknake kill-9 |
Summary of the Node.js Board controversy from what I can gather.
All the redactions (and hidden/private conversations) has made it very hard for the outside to figure out what has occured.
Node.js Community Committee wanted Rod out:
if (!process.browser) var sodium = require('sodium-native') | |
var blake2b = require('blake2b') | |
var blake2bw = require('blake2b-wasm') | |
var BLAKE2s = require('blake2s-js') | |
var crypto = require('crypto') | |
var DATA_64KB = Buffer.alloc(65536) | |
var DATA_4KB = Buffer.alloc(4096) | |
var DATA_128B = Buffer.alloc(128) |
# LVDB - LLOOGG Memory DB | |
# Copyriht (C) 2009 Salvatore Sanfilippo <antirez@gmail.com> | |
# All Rights Reserved | |
# TODO | |
# - cron with cleanup of timedout clients, automatic dump | |
# - the dump should use array startsearch to write it line by line | |
# and may just use gets to read element by element and load the whole state. | |
# - 'help','stopserver','saveandstopserver','save','load','reset','keys' commands. | |
# - ttl with milliseconds resolution 'ttl a 1000'. Check ttl in dump! |