You have installed GPG, then tried to perform a git commit and suddenly you see this error message after it 😰
error: gpg failed to sign the data
fatal: failed to write commit object
Understand the error (important to solve it later!)
| Regex for matching ALL Japanese common & uncommon Kanji (4e00 – 9fcf) ~ The Big Kahuna! | |
| ([一-龯]) | |
| Regex for matching Hirgana or Katakana | |
| ([ぁ-んァ-ン]) | |
| Regex for matching Non-Hirgana or Non-Katakana | |
| ([^ぁ-んァ-ン]) | |
| Regex for matching Hirgana or Katakana or basic punctuation (、。’) |
| #!/bin/bash | |
| # from | |
| # http://bergamini.org/computers/creating-favicon.ico-icon-files-with-imagemagick-convert.html | |
| convert source-WxW.png -resize 256x256 -transparent white favicon-256.png | |
| convert favicon-256.png -resize 16x16 favicon-16.png | |
| convert favicon-256.png -resize 32x32 favicon-32.png | |
| convert favicon-256.png -resize 64x64 favicon-64.png | |
| convert favicon-256.png -resize 128x128 favicon-128.png |
See how a minor change to your commit message style can make a difference.
git commit -m"<type>(<optional scope>): <description>" \ -m"<optional body>" \ -m"<optional footer>"
| /* | |
| * ------------------------------------------------------------ | |
| * "THE MONSTERWARE LICENSE" (Revision 01): | |
| * <author> wrote this code. As long as you retain this | |
| * notice, you can do whatever you want with this stuff. If we | |
| * meet someday, and you think this stuff is worth it, you can | |
| * buy me a Monster Energy® energy drink in return. | |
| * ------------------------------------------------------------ | |
| */ |
| // Learn more https://next-auth.js.org/configuration/providers | |
| import type { NextApiRequest, NextApiResponse } from 'next' | |
| import NextAuth from 'next-auth' | |
| import Providers from 'next-auth/providers' | |
| const options = { | |
| providers: [ | |
| Providers.Facebook({ | |
| clientId: process.env.FACEBOOK_ID, |
I've experimented with Kotlin and coroutines in programming Akka. And I must say, I really like the combination so far.
But before I go into it some brief preliminaries for those who don't know Akka and actors.
Actors are a programming model that fits cloud native architectures particularly well. Being highly available and scaling horizontally. All while embracing the realities of multiple servers collaborating, server instances coming and going and the network having hickups.
On the JVM Akka is the prominent actor framework. It's been around for a while now and as a result it's highly reliable, well thought out and offers a wide programming eco system. My own interest in Akka is because of its suitability for software systems that can only be built with business events as a key construct and thinking model. And then of course materialized views, CQRS and near real-time data streams play a big role in constructing those systems.
For anyone considering the use of ULIDs in MySQL with drizzle, here's a ready-to-use ULID type for your convenience.
import { Ulid as ULID } from "id128";
export const ulid = customType<{
data: string;
notNull: true;
default: false;| #!/usr/bin/env bash | |
| function house_builder() { | |
| # floors,rooms,has_garage | |
| echo "0,0,0" | |
| } | |
| function set_field() { | |
| local f r g | |
| IFS=, read f r g |