Aaron Batilo abatilo

How to use channels across different processes in Go

A couple of code samples to show how a named pipe can be used to extend Go's channel paradigm for use between different processes running on a system.

interprocess1.go details a single byte channel.
interprocess2.go details a channel that passes slices of bytes.

Note that opening a write channel will return two channels -

Keybase proof

I hereby claim:

I am abatilo on github.
I am abatilo (https://keybase.io/abatilo) on keybase.
I have a public key ASBj4Bn3TezS05hHpJOC9GEht3EPE2hH8UCfVnGGI-YacQo

To claim this, I am signing this object:

	FROM ubuntu:22.04

	# Install sshd and xz to unzip the s6-overlay tarball
	RUN <<EOF
	apt-get update;
	apt-get install -yq openssh-server xz-utils;
	EOF

	# Install s6-overlay
	ADD https://github.com/just-containers/s6-overlay/releases/download/v3.1.6.2/s6-overlay-noarch.tar.xz /tmp

	export ZSH="$HOME/.oh-my-zsh"
	ZSH_THEME="pygmalion"

	plugins=(
	mise
	fzf
	git
	kubectl
	)

	package gogptindex

	import (
	"context"
	_ "embed"
	"encoding/json"
	"fmt"
	"net/http"
	"os"
	"os/signal"

	apiVersion: apps.kruise.io/v1alpha1
	kind: ImagePullJob
	metadata:
	name: sudokurace
	namespace: kruise-system
	spec:
	image: '911907402684.dkr.ecr.us-west-2.amazonaws.com/sudokurace:' # Tag set by kustomization.yaml
	pullSecrets:
	# Must match https://gist.github.com/abatilo/6b287265d541d06da567893c1522999f#file-imagepulljob-tf-L3
	- kruise-ecr-token

	locals {
	kruise_ecr_token_updater_service_account = "kruise-ecr-token-updater"
	kruise_ecr_token_secret_name = "kruise-ecr-token"

	kruise_ecr_token_updater_script = <<EOF
	ECR_TOKEN=`aws ecr get-login-password --region $${AWS_REGION}`
	NAMESPACE_NAME=${kubernetes_namespace.kruise_system.metadata[0].name}

	kubectl delete secret --ignore-not-found $DOCKER_SECRET_NAME -n $NAMESPACE_NAME
	kubectl create secret docker-registry $DOCKER_SECRET_NAME \

	name: Print rate limits
	on:
	push:

	jobs:
	rate-limit:
	runs-on: ubuntu-latest
	steps:
	- name: Generate token
	id: generate_token

	DROP TABLE IF EXISTS sent;
	DROP TABLE IF EXISTS message;
	DROP TABLE IF EXISTS recipient;

	CREATE TABLE IF NOT EXISTS recipient (
	id serial primary key
	);

	CREATE TABLE IF NOT EXISTS message (
	id serial primary key