Arnav Bansal lunaroyster

Keybase proof

I hereby claim:

I am thel3l on github.
I am thel3l (https://keybase.io/thel3l) on keybase.
I have a public key whose fingerprint is B31B 7D96 BFC5 C027 134E 7051 1E72 8F19 348C 5779

To claim this, I am signing this object:

The new Bitcoin Cash address format ("Cash Address")

On ~January 14, the Bitcoin Cash clients will (we expect huge adoption) switch to the new Cash Address address format.

Related to Bech32?

Bech32 is the name of the address format proposed by Core developers (for SegWit addresses,BIP 173. It consists of 32 different characters, and "Bech" sounds like "Base" while keeping the error-correction algorithm "BCH" (or Bitcoin Cash ticker!) in mind. Bitcoin Cash will use a slightly different Bech32 address format, which is called "Cash Address".

So what?

Interactive Debugging on Github Actions

Did you ever run into some issue where a job would behave slightly different in you CI environment than on your local machine? Did you ever wish you could run just a few commands in a shell on your build machine?

These are, of course rhetorical questions. And if you're using Github Actions to run your CI jobs, you'll have noticed that this use case is not supported at all. Can't create a nice walled garden if anyone could just run a CI job, after all. There are some workarounds (e.g. https://github.com/nektos/act), but since they're not officially supported they can be a bit unstable. Also, even they usually don't reproduce the exact environment found on github's servers.

	// POLYFILLS
	// Event.composedPath
	// Possibly normalize to add window to Safari's chain, as it does not?
	(function(E, d, w) {
	if(!E.composedPath) {
	E.composedPath = function() {
	if (this.path) {
	return this.path;
	}
	var target = this.target;