Riebart

#!/usr/bin/env python

# Source: https://stackoverflow.com/questions/12977179/reading-living-process-memory-without-interrupting-it
#
# Adapted to be python3

import os
import re
import sys

Riebart

#!/usr/bin/env python3

# GPU Search by string:
#  "https://www.3dmark.com/proxycon/ajax/search/gpuname?term=" + s

import json
import requests
import time
import sys

Riebart

$session=(query session | select-string Active)[0].ToString().split(" ")[0].substring(1)
Start-Process -verb runas tscon -ArgumentList "$session /dest:console"

Riebart

Syslog logging levels and parameters

All logs

All logs should contain the following information, preferably encoded in JSON so that it is easily machine-parsable as well as human readable. Graylog can parse JSON, so encoding your fields in that way makes it easy to alert and filter on messaged components.

• Message: The message should be a plaintext description of the event, optionally including an application-unique code.
• Impact: This field should describe the impact, if any (there is no impact for debug and informational events), on the state, output, and resiliency of the application. It should be short (one sentence), but contain enough information for someone not familiar with the application to triage the event.
• Correction: This field should describe any corrective action, if any (there is no corrective action required for debug, informational, and notice level events), that could, or should, be taken to resolve the impacts caused by the event. This should be short (at most two sentences) an

Riebart

Comparing branching and workflow strategies

Summary of existing

There's several existing strategies for deploying and managing development work and release. They each have their own opinions, but roughly cover a few major situations:

• Developing a new feature
• Which branches should be, at all times, deployable, tested code
• Under what conditions a code review or approval is required to merge code into a new branch
• How many deployment environments (e.g. production only, or staging and production) you intend to have available, and to whom

Riebart

#!/bin/bash

ffmpeg \
  -ss 90.75 -i "input1.mp4" \
  -ss 0 -i "input2.mp4" \
  -filter_complex "\
    [0:v]setpts=PTS-STARTPTS,crop=iw/2:ih:iw/4:0[leftRaw];\
    [1:v]setpts=PTS-STARTPTS,crop=iw/2:ih:iw/4:0[rightRaw];\
    [leftRaw]scale=-1:1080[left];\
    [rightRaw]scale=-1:1080[right];\

Riebart

votesPerState = {{"Alabama", 9.`}, {"Alaska", 3.`}, {"Arizona", 
     11.`}, {"Arkansas", 6.`}, {"California", 55.`}, {"Colorado", 
     9.`}, {"Connecticut", 7.`}, {"Delaware", 
     3.`}, {"DistrictOfColumbia", 3.`}, {"Florida", 29.`}, {"Georgia",
      16.`}, {"Hawaii", 4.`}, {"Idaho", 4.`}, {"Illinois", 
     20.`}, {"Indiana", 11.`}, {"Iowa", 6.`}, {"Kansas", 
     6.`}, {"Kentucky", 8.`}, {"Louisiana", 8.`}, {"Maine", 
     4.`}, {"Maryland", 10.`}, {"Massachusetts", 11.`}, {"Michigan", 
     16.`}, {"Minnesota", 10.`}, {"Mississippi", 6.`}, {"Missouri", 
     10.`}, {"Montana", 3.`}, {"Nebraska", 5.`}, {"Nevada", 

Riebart

#!/bin/bash

# DEPENDENCIES:
#  - jq: https://stedolan.github.io/jq/
#  - pup: https://github.com/EricChiang/pup
#  - python-Levenshtein: https://pypi.org/project/python-Levenshtein/
#  - You'll need a Steam API key, which you can get from https://steamcommunity.com/dev/apikey

# USAGE:
#  This pulls in the full steam app list from the API, your user's game list via the Steam API,

Riebart

#!/usr/bin/env python3

import time
import uuid
import random
import re
import sys

import requests

Riebart

interfaces {
    ethernet eth1 {
        address 10.0.0.1/24
        address 192.168.100.1/24
        address ffff:ffff:ffff:ffff::1/64
        address ffff:ffff:ffff:ffff::1/64
        description Athens
        duplex auto
        firewall {
            local {