mrWinston

How to run

• install libevdev: pip install libevdev

• open rnote (or xournal++)

• run python ./run.py

• Cursor should move the the rnote window and the rnote window will be killed.

  • If the cursor doesn't end up on the rnote window, tweak the ABS_X and ABS_Y values in the code until you hit the right spot.

• If you get a permission error try running as root. It needs write access to /dev/uinput to send the input events

mrWinston

{
    "output": {
        "blocklist": [],
        "equalizer": {
            "balance": 0.0,
            "bypass": false,
            "input-gain": 0.0,
            "left": {
                "band0": {
                    "frequency": 146.0,

mrWinston

CopySheet

Signal

• Get the App:
  • Android
  • IOS
  • other
• Register usig your phone number
  • docs

mrWinston

#!/bin/bash

# either run this script to trigger the update, or copy the function below to your .bash/.zshrc and run with `asdfUpdateAll`
# the function also supports `--yes` to disable confirmation for updating a plugin.

asdfUpdateAll() {
  if ! asdf > /dev/null; then
    echo "Something went wrong when running 'asdf'"
    return 1
  fi

mrWinston

How to set up Midi over Bluetooth with Bitwig under Ubuntu 22.04

Getting Midi over Bluetooth (MoB) to work together with Bitwig under Ubuntu 22.04 requires you to jump through a few hoops. Two main issues need to be navigated around:

1. The ubuntu userspace bluetooth driver does not have midi enabled
2. Bitwig only accepts hardware Midi devices, while MoB creates a software midi device

Fixing the first requires us to build bluez from scratch and enable the midi functionality as a compiler flag: https://tttapa.github.io/Pages/Ubuntu/Software-Installation/BlueZ.html

mrWinston

{
    "output": {
        "blocklist": [],
        "equalizer": {
            "balance": 0.0,
            "bypass": false,
            "input-gain": 0.0,
            "left": {
                "band0": {
                    "frequency": 65.0,

mrWinston

How to run the osde2e tests locally

This short guide shows you how to setup the e2e tests on your local machine. We won't go into detail on how all of the e2e stuff works, as this is covered in great detail in the osde2e documentation itelf. Instead, i'll just focus on the steps I took to get them running locally, without too many tangents.

Prerequisites

1. Fork and clone the osde2e test repo: gh.com/openshift/osde2e
2. Make sure you have an osd cluster ready
3. golang version 1.16+

mrWinston

PR Title

Fixes: OSD-12345

• Explain what
• the PR does
• To the code.
• What problems does it solve

Testing instructions

mrWinston

#!/bin/bash

tmpfile="$(mktemp)"
# Make sure the temp directory gets removed on script exit.
trap "exit 1"             HUP INT PIPE QUIT TERM
trap rm -rf   EXIT

mrWinston

#/bin/bash
set -euo pipefail

monitoringPodList="$(oc -n openshift-monitoring get pods)"

firstDelete=(
  "openshift-monitoring/alertmanager-main-0"
  "openshift-monitoring/prometheus-k8s-0"
  "openshift-monitoring/$(echo "$monitoringPodList" | grep "grafana" | awk '{print $1}')"
  "openshift-monitoring/$(echo "$monitoringPodList" | grep "telemeter-client" | awk '{print $1}')"