Discover gists

The problem

WSL2 uses a random network from the 172.16.0.0/12 RFC1918 private IP address block. And our VPN uses that address block, too, with a route metric of 1 (= most preferred.)

This breaks networking for WSL2. Meh!

The solution

While messing around with the interface/route metric of the VPN network may work around the problem, it also reduces the priority of the VPN. We do not really want this. Additionally, changing the interface metric does not seem to be permanent, so it requires more work when it breaks again.

A metatable can be defined like

local t = setmetatable({}, {
  __tostring = function() return 'custom tostring behavior!' end
})

Here are the metamethods that you can define, and their behavior

Operators

DaVinci Resolve Scripting Documentation

Updated as of 08 March 2019

In this package, you will find a brief introduction to the Scripting API for DaVinci Resolve Studio. Apart from this README.txt file, this package contains folders containing the basic import modules for scripting access (DaVinciResolve.py) and some representative examples.

Overview

As with Blackmagic Design Fusion scripts, user scripts written in Lua and Python programming languages are supported. By default, scripts can be invoked from the Console window in the Fusion page, or via command line. This permission can be changed in Resolve Preferences, to be only from Console, or to be invoked from the local network. Please be aware of the security implications when allowing scripting access from outside of the Resolve application.

Configuring xdebug to work with Windows 10 (WSL2), Docker and VS Code

Configuring your dev environment to be able to use xdebug when you're working on Windows 10 (with WSL2) and Docker with VS Code can be (a bit) tricky.
This is a quick reminder of how I've done that.

Configuring the environment

Install and configure xdebug in Docker

Install xdebug according to the Docker image you're using

	Windows Registry Editor Version 5.00

	[HKEY_CLASSES_ROOT\*\shell\runas]
	@="Take Ownership"
	"NoWorkingDirectory"=""

	[HKEY_CLASSES_ROOT\*\shell\runas\command]
	@="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F"
	"IsolatedCommand"="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F"

	#!/usr/bin/env ruby

	# this scripts acts as a wrapper for a little daemon that reads a fifo;
	#
	# If called without allready running it starts a background daemon and
	# downloads the argument, then proceeds to watch the fifo for more.
	#
	# We esnure that the script is only running once and only one dl at a time.

	FIFO = "/home/ha/.ytfifo"

	#!/bin/bash
	# Sometimes you need to move your existing git repository
	# to a new remote repository (/new remote origin).
	# Here are a simple and quick steps that does exactly this.
	#
	# Let's assume we call "old repo" the repository you wish
	# to move, and "new repo" the one you wish to move to.
	#
	### Step 1. Make sure you have a local copy of all "old repo"
	### branches and tags.

	package util

	import (
	"errors"
	"fmt"
	"net"
	)

	// useful links:
	// https://stackoverflow.com/questions/27410764/dial-with-a-specific-address-interface-golang

	## Pre-requisite: You have to know your last commit message from your deleted branch.
	git reflog
	# Search for message in the list
	# a901eda HEAD@{18}: commit: <last commit message>

	# Now you have two options, either checkout revision or HEAD
	git checkout a901eda
	# Or
	git checkout HEAD@{18}