evgeny-goldin

# Validate project's JSON files 
function vj()
{
  if [ "$1" == "" ]; then
    local path="."
  else
    local path="$1"
  fi  
  
  for json in $(find "$path" -name "*.json"); do

roman

(ns rx.example.schedulers
  (:require
   [monads.core :refer [Monad] :as monad]
   [clojure.core.match :refer [match]]
   [disposables.core :as disposable]
   [com.unbounce.treajure.io :as tio]
   [rx.lang.clojure.core :as rx]
   [clj-http.client :as http])
  (:import
   [java.util.concurrent Executors]

lewisd32

echo "Flipping tables! (╯°□°）╯︵ ┻━┻"

num_rules=3

real=3    # exposed to the ELB as port 443
test=4    # used to install test certs for domain verification
health=5  # used by the ELB healthcheck

blue_prefix=855
green_prefix=866

apangin

_hashCode                               java/lang/Object.hashCode()I
_getClass                               java/lang/Object.getClass()Ljava/lang/Class;
_clone                                  java/lang/Object.clone()Ljava/lang/Object;
_dabs                                   java/lang/Math.abs(D)D
_dsin                                   java/lang/Math.sin(D)D
_dcos                                   java/lang/Math.cos(D)D
_dtan                                   java/lang/Math.tan(D)D
_datan2                                 java/lang/Math.atan2(DD)D
_dsqrt                                  java/lang/Math.sqrt(D)D
_dlog                                   java/lang/Math.log(D)D

peterflynn

To use: create a new bookmark and paste into the URL field.

In Chrome, you can paste the full multiline code as shown below.
In other browsers, you may need to minify the code into one line first.

ddossot

OPTIONS=`vagrant ssh-config | grep -v '^Host ' | awk -v ORS=' ' 'NF{print "-o " $1 "=" $2}'`

To copy a file from the host to a Vagrant VM:

scp ${OPTIONS} $FILE v:$PATH

to copy a file from a Vagrant VM to the host:

scp ${OPTIONS} v:$PATH $FILE

antirez

RESP3 specification

Versions history:

• 1.0, 2 May 2018, Initial draft to get community feedbacks.

Background

The Redis protocol has served us well in the past years, showing that, if carefully designed, a simple human readable protocol is not the bottleneck in the client server communication, and that the simplicity of the design is a major advantage in creating a healthy client libraries ecosystem.

Yet the Redis experience has shown that after about six years from its introduction (when it replaced the initial Redis protocol), the current RESP protocol could be improved, especially in order to make client implementations simpler and to support new features.