robmiller

#
# Working with branches
#

# Get the current branch name (not so useful in itself, but used in
# other aliases)
branch-name = "!git rev-parse --abbrev-ref HEAD"
# Push the current branch to the remote "origin", and set it to track
# the upstream branch
publish = "!git push -u origin $(git branch-name)"

ducin

"""
Console module provide `copen` method for opening interactive python shell in
the runtime.
"""

import code
import readline
import rlcompleter

def copen(_globals, _locals):

sloria

The Best of the Best Practices (BOBP) Guide for Python

A "Best of the Best Practices" (BOBP) guide to developing in Python.

In General

Values

• "Build tools for others that you want to be built for you." - Kenneth Reitz
• "Simplicity is alway better than functionality." - Pieter Hintjens

smithclay

Recipe for running strange binaries in AWS Lambda

In general, the command ldd and the environment variable LD_LINKER_PATH is your best friend when running new, untested binaries in Lambda. My process (which I want to get around to automating one day, maybe using Packer), goes like this:

1. Run an EC2 instance with the official AWS Lambda AMI.
2. Get binary you want to run in AWS Lambda running on the instance (either by installing from a package manager or compiling). 
3. Run ldd -v ./the-binary. Note all of the shared libraries it requires. You’ll need to remember these.
4. Copy the binary to your local machine. Upload the binary with your AWS Lambda function code that runs the ldd command inside the handler function using the process execution library from your language of choice. In node, this works just fine: console.log(require('child_process').execSync('ldd -v ./the-binary'))
5. Note any shared libraries that are missing in the function output. Copy those over from the EC2 instance to a direct

ivan3bx

// runServer will start the HTTPServer, handling graceful
// shutdown on receives SIGTERM / SIGINT, returning nil.
//
// - returns error if the server can not start
// - returns error if the server panics in a way that isn't
//   otherwise handled by gin
// - no errors otherwise
func runServer(addr string, r *gin.Engine) error {
	s := &http.Server{
		Addr:         addr,

hantoine

from urllib.request import urlopen
from io import BytesIO
from zipfile import ZipFile
from subprocess import Popen
from os import chmod
from os.path import isfile
import json
import time
import psutil

hantoine

Argo in Kind

Play with "Argo Workflow" in your local kind cluster.

Prerequisites

The following instructions were tested in macOS Monterey (12.4), on 10 Jul 2022.

Docker Runtime

Ensure docker is installed and running.

K8s Client