Jason Pickens steinybot

A guide for using emojis in pull requests to clearly indicate the purpose of the comment.

Emoji	Tag	Description	Blocking (✅ Yes, ❌ No)
🐛	`:bug:`	I think there might be a bug here	✅
❓	`:question:`	I have a question about this	✅
📝	`:memo:`	You should document this	✅
♻️	`:refactor:`	You should refactor this	✅
🛠️	`:hammer_and_wrench:`	You should change this	✅
😍 / 🌈	`:heart_eyes:` / `:rainbow:`	This is beautiful. Kudos!	❌

Debugging pekko streams

From org.apache.pekko.stream.impl:

 *   * [[org.apache.pekko.stream.impl.PhasedFusingActorMaterializer.Debug]]: if this flag is turned on, the materializer will
 *     log the steps it takes
 *   * [[org.apache.pekko.stream.impl.TraversalBuilder.printTraversal]]: Prints the Traversal in a readable format
 *   * [[org.apache.pekko.stream.impl.TraversalBuilder.printWiring]]: Prints the calculated port assignments. Useful for

Named Functions

`COLUMNADDRESS`

Column reference as a string.

Arguments:

Name	Description	Example

graphql/graphql-spec#1038

I'm sure there must be a reason (valid or historical) but distinguishing between input and output types seems to serve no real purpose and comes with a significant cost.

By no means the authority but perhaps a good starting point are the reasons that ChatGPT give:

In GraphQL, the distinction between regular types (also known as output types) and input types serves a specific purpose to ensure clarity, maintainability, and type safety. While it might seem convenient to use any type as an input type, there are valid reasons for this separation:

Please ChatGPT, do tell...

    // TODO: Determine whether we need traceKitWindowOnError to map the errors too.
    dom.window.asInstanceOf[std.Window].onerror = toUnionLeft(onErrorEventHandler _)

  private def onErrorEventHandler(
    event: dom.Event | String,
    source: js.UndefOr[String],
    lineno: js.UndefOr[Double],

scalacOptions ++= Seq(
  "-Ybrowse:typer",
  "-Xprint:typer",
  "-Xlog-implicits"
)

Nix Tips

Build a package from a different system (e.g. run Intel package under Rosetta 2):

nix-build -A pkgsCross.x86_64-darwin.hello

Run nix-shell with local packages:

nix-shell -I nixpkgs=/Users/jason/src/nixpkgs

New MacBook Setup

For the automated setup run:

sh <(curl -L https://gist.githubusercontent.com/steinybot/085ef82571f4416506388c6a1e58637a/raw/9d71a417534813082fd02a4820eff92420c45040/bootstrap.sh)

For the manual setup follow the steps below:

	package stripe

	import slinky.core.ExternalComponent
	import slinky.core.annotations.react

	import scala.scalajs.js
	import scala.scalajs.js.annotation.JSImport
	import scala.scalajs.js.\|

	@react

	#!/usr/bin/env bash
	set -euo pipefail

	# Ever move a file, merge main, then get hit with this?
	#
	# Deleted merge conflict for 'foo.txt':
	# {local}: deleted
	# {remote}: modified file
	# Use (m)odified or (d)eleted file, or (a)bort?
	#