TangerineCat

graph Doskvol {
    concentrate=true;
    edge[color=forestgreen]
    subgraph legend {
        color = black;
        label = "Legend";
        "Tier I"--"Tier II"--"Tier III"--"Tier IV"--"Tier V"
    }
    
    

leophys

### colored and fuzzy go doc
if which bat > /dev/null; then
  function _godoc() {
    if echo $1|grep -q -E "^([a-zA-Z0-9/]+)$"; then
      go doc ${@} | bat -p -l md
    elif echo $1|grep -q -E "^[a-zA-Z0-9/]+\.[a-zA-Z0-9.]+$"; then
      go doc ${@} | bat -p -l go
    elif echo $1|grep -q -E "^([a-zA-Z0-9/._-]+)/.*\.[a-zA-Z0-9.]+$"; then
      go doc ${@} | bat -p -l go
    else

wijayaerick

// ConsoleHandler formats slog.Logger output in console format, a bit similar with Uber's zap ConsoleEncoder
// The log format is designed to be human-readable. 
// 
// Performance can definitely be improved, however it's not in my priority as 
// this should only be used in development environment.
//
// e.g. log output:
// 2022-11-24T11:40:20+08:00 DEBUG ./main.go:162 Debug message {"hello":"world","!BADKEY":"bad kv"}
// 2022-11-24T11:40:20+08:00 INFO ./main.go:167 Info message {"with_key_1":"with_value_1","group_1":{"with_key_2":"with_value_2","hello":"world"}}
// 2022-11-24T11:40:20+08:00 WARN ./main.go:168 Warn message {"with_key_1":"with_value_1","group_1":{"with_key_2":"with_value_2","hello":"world"}}

iNetJoJo

package workload

import (
	"context"
	"golang.org/x/sync/errgroup"
	"time"
)

type Worker func() error

StevenACoffman

package main

import (
	"context"
	"encoding/json"
	"errors"
	"fmt"
	"log"
	"net/http"
	"os"

preslavrachev

package do

type Void struct{}

type Result[T any] interface {
	Unwrap() (T, error)
}

type defaultResult[T any] struct {
	val T

lawrencejones

pkg/errors

Our incident.io pkg/errors, as explained in:

• https://incident.io/blog/golang-errors

StevenACoffman

From The 7 Types of Pull Requests:

After reading Rouan Wilsenach’s article on Ship / Show / Ask, I realized that when creating a pull request, I’m thinking about:

• How can I confidently get my code out of the door?
• Will my changes pass the automated CI checks?
• Will my changes pass a self-review? I.e. would I approve my own PR?
• Will my colleagues be able to give me good feedback?

So this gives us 7 types of pull-request:

No Pull Request / Ship

StevenACoffman

1. If you have a particular StackOverflow question such as:

• https://stackoverflow.com/questions/69419055/find-the-pseudo-version-of-the-current-main-module

2. When you click on the little recylcing symbol next to a question or answer "Show activity on this post", you will get to the timeline:

https://stackoverflow.com/posts/69419917/timeline#history_9281a690-64c3-4302-bb36-1ebb6dfd3ecf

3. Take the post ID that is exposed in the timeline url as above

Go to Question revision history:

rafi

K3d and Keycloak

Prerequisites

Ensure docker, k3d and ngrok are installed.

brew update
brew install --cask docker ngrok
brew install k3d