pathcl

Data for this

https://www.kaggle.com/datasets/alexpunnen/wikipedia-history-of-save-failures

Running in Docker Container

docker run --rm -it --net=host -v /home/xxx:/home alexcpn/fb_prophet_python:1 cd /home/xx//python python outlier_full.py

pathcl

sudo gitlab-rails console
ApplicationSetting.last.update_attributes(signin_enabled: true)
exit
sudo gitlab-ctl restart

pathcl

#!/bin/bash
# USAGE: CLUSTER=mycluster SERVICE=myservice ./docker-exec-ecs.sh
set -euf -o pipefail

TASK_ARN=$(aws ecs list-tasks --cluster=$CLUSTER --service=$SERVICE \
           | jq -r .taskArns[0])
if [ "$TASK_ARN" = "null" ]; then
  echo "Could not find any running tasks for $SERVICE on cluster:$CLUSTER."
  exit 1
fi

pathcl

Latency Comparison Numbers (~2012)
----------------------------------
L1 cache reference                           0.5 ns
Branch mispredict                            5   ns
L2 cache reference                           7   ns                      14x L1 cache
Mutex lock/unlock                           25   ns
Main memory reference                      100   ns                      20x L2 cache, 200x L1 cache
Compress 1K bytes with Zippy             3,000   ns        3 us
Send 1K bytes over 1 Gbps network       10,000   ns       10 us
Read 4K randomly from SSD*             150,000   ns      150 us          ~1GB/sec SSD

pathcl

'''
Basic tail command implementation
Usage:

tail.py filename numlines

'''

import sys
import linecache

pathcl

How to config rabbitmq server cluster [3 nodes]

Edit /etc/hosts

vi /etc/hosts
192.168.10.157  rabbitmq-1
192.168.10.159  rabbitmq-2
192.168.10.161  rabbitmq-3

pathcl

git config --global url."https://github.com/".insteadOf [email protected]:
git config --global url."https://".insteadOf git://

pathcl

tmux cheat sheet

(C-x means ctrl+x, M-x means alt+x)

Prefix key

The default prefix is C-b. If you (or your muscle memory) prefer C-a, you need to add this to ~/.tmux.conf:

remap prefix to Control + a

pathcl

In your local clone of your forked repository, you can add the original GitHub repository as a "remote". ("Remotes" are like nicknames for the URLs of repositories - origin is one, for example.) Then you can fetch all the branches from that upstream repository, and rebase your work to continue working on the upstream version. In terms of commands that might look like:

Add the remote, call it "upstream":

git remote add upstream https://github.com/whoever/whatever.git

Fetch all the branches of that remote into remote-tracking branches, such as upstream/master:

git fetch upstream

pathcl

package main

import (
	"context"
	"github.com/go-chi/chi"
	"github.com/go-chi/render"
	"github.com/prometheus/client_golang/prometheus"
	"github.com/prometheus/client_golang/prometheus/promhttp"
	log "github.com/sirupsen/logrus"
	"gopkg.in/olivere/elastic.v6"