tylermorganwall

library(geojsonsf)
library(sf)
library(rayrender)

#Data source: https://github.com/telegeography/www.submarinecablemap.com
cables = geojson_sf("cable-geo.json")

cablescene = list()
counter = 1
for(i in 1:length(cables$geometry)) {

fxkraus

download

wget https://docs.broadcom.com/docs-and-downloads/raid-controllers/raid-controllers-common-files/8-07-14_MegaCLI.zip

unzip

unzip 8-07-14_MegaCLI.zip

ipbastola

JQ to filter JSON by value

Syntax: cat <filename> | jq -c '.[] | select( .<key> | contains("<value>"))'

Example: To get json record having _id equal 611

cat my.json | jq -c '.[] | select( ._id | contains(611))'

Remember: if JSON value has no double quotes (eg. for numeric) to do not supply in filter i.e. in contains(611)

FZambia

package main

import (
	"bytes"
	"encoding/json"
	"os/exec"

	"gopkg.in/xmlpath.v2"
)

jvkersch

I found this information somewhere on StackOverflow but I forgot exactly where. I'm paraphrasing what I learned here, for future reference.

SSH uses a Unix socket to communicate with other processes. The socket's path can be found by looking at the environment variable $SSH_AUTH_SOCK. When you re-connect to a tmux session that was started during a previous SSH session, this variable will contain the path of the previous SSH auth socket, and this will cause processes that try to connect to your authentication agent to fail. To fix this, we have to

1. Create a symlink from the auth socket to a fixed path somewhere, so that we can refer to it later on. In ~/.ssh/rc, add

if test "$SSH_AUTH_SOCK"; then
	ln -sf $SSH_AUTH_SOCK ~/.ssh/ssh_auth_sock
fi

u0d7i

Disable vim automatic visual mode on mouse select

issue: :set mouse-=a
add to ~/.vimrc: set mouse-=a

my ~/.vimrc for preserving global defaults and only changing one option:

source $VIMRUNTIME/defaults.vim
set mouse-=a

wincent

2015-01-29 Unofficial Relay FAQ

Compilation of questions and answers about Relay from React.js Conf.

Disclaimer: I work on Relay at Facebook. Relay is a complex system on which we're iterating aggressively. I'll do my best here to provide accurate, useful answers, but the details are subject to change. I may also be wrong. Feedback and additional questions are welcome.

What is Relay?

Relay is a new framework from Facebook that provides data-fetching functionality for React applications. It was announced at React.js Conf (January 2015).

caike

NodeJS Streams

• Current implementation is known as streams2.
• Introduced in node v0.10.
• "suck" streams instead of "spew" streams.
• Instead of data events spewing, call read() to pull data from source.
• When there isn't any data to consume, then read() will return undefined.
• Adding a data event listener will switch the Readable stream into "old mode", where data is emitted as soon as it is available rather than waiting for you to call read() to consume it. This requires you to handle backpressure problems manually.
• The pipe method helps write less code and handles back-pressure.
• If you add an end listener and don't ever read() or pipe(), it'll never emit end.

zachleat

Guides:

http://pragtob.wordpress.com/2014/01/13/how-to-get-started-with-contributing-to-open-source/
http://movethewebforward.org/
http://www.smashingmagazine.com/2011/11/30/the-smashing-guide-to-moving-the-web-forward-community/
http://nshipster.com/stewardship/
https://speakerdeck.com/brycekahle/helping-open-source-software

for Designers:

joyrexus

A quick overview of the node.js streams interface with basic examples.

This is based on @brycebaril's presentation, Node.js Streams2 Demystified

Overview

Streams are a first-class construct in Node.js for handling data.

Think of them as as lazy evaluation applied to data.