Category Archives: Programming

«Awesome go» resources

A list of good resources for each go specific part — https://github.com/avelino/awesome-go. A list of good tools for go performance or just fast libs — https://github.com/cristaloleg/awesome-go-perf Security lists — https://github.com/guardrailsio/awesome-golang-security, https://github.com/Binject/awesome-go-security

Go library for creating slack bots

You can use it like that:

package main

import (
	"context"
	"github.com/shomali11/slacker"
	"log"
)

func main() {
	bot := slacker.NewClient("<YOUR SLACK BOT TOKEN>")

	definition := &slacker.CommandDefinition{
		Handler: func(request slacker.Request, response slacker.ResponseWriter) {
			response.Reply("pong")
		},
	}

	bot.Command("ping", definition)

	ctx, cancel := context.WithCancel(context.Background())
	defer cancel()

	err := bot.Listen(ctx)
	if err != nil {
		log.Fatal(err)
	}
}

package main

import (

"context"

"github.com/shomali11/slacker"

"log"

)

func main() {

bot := slacker.NewClient("<YOUR SLACK BOT TOKEN>")

definition := &slacker.CommandDefinition{

Handler: func(request slacker.Request, response slacker.ResponseWriter) {

response.Reply("pong")

}

bot.Command("ping", definition)

ctx, cancel := context.WithCancel(context.Background())

defer cancel()

err := bot.Listen(ctx)

if err != nil {

log.Fatal(err)

}

https://github.com/shomali11/slacker

How to work with core dumps of Go programs

If you want to check what is going on in your service during load (on production or during stress testing process), you can take a core dump of your app and load it into Goland for further debugging.

# first you need to get your app's PID
ps aux|grep <your-app-bin-name> 
gcore <PID>
# download dump file and binary file to a local machine with
kubectl cp <some-namespace>/<some-pod>:/core.<PID> ~/Downloads
kubectl cp <some-namespace>/<some-pod>:<your-app-bin-path> ~/Downloads

# first you need to get your app's PID

ps aux|grep <your-app-bin-name>

gcore <PID>

# download dump file and binary file to a local machine with

kubectl cp <some-namespace>/<some-pod>:/core.<PID> ~/Downloads

kubectl cp <some-namespace>/<some-pod>:<your-app-bin-path> ~/Downloads

Then open it your Goland: Navigate to Run | Open Core Dump. In the Executable field, …

Nice introductory article on why Golang is not OOP

It is a copy of this article — https://rakyll.org/typesystem/ It is real struggle to work with a new language, especially if the type doesn’t resemble what you have previously seen. I have been there with Go and lost my interest in the language when it first came out due to the reason I was pretending …

A way to test http client in go

A couple of ways are described here — http://hassansin.github.io/Unit-Testing-http-client-in-Go The way I liked is the following one:

func Test_Mine(t *testing.T) {
    ...
    client := httpClientWithRoundTripper(http.StatusOK, "OK")
    ...
}

type roundTripFunc func(req *http.Request) *http.Response

func (f roundTripFunc) RoundTrip(req *http.Request) (*http.Response, error) {
	return f(req), nil
}

func httpClientWithRoundTripper(statusCode int, response string) *http.Client {
	return &http.Client{
		Transport: roundTripFunc(func(req *http.Request) *http.Response {
			return &http.Response{
				StatusCode: statusCode,
				Body:       ioutil.NopCloser(bytes.NewBufferString(response)),
			}
		}),
	}
}

func Test_Mine(t *testing.T) {

...

client := httpClientWithRoundTripper(http.StatusOK, "OK")

...

}

type roundTripFunc func(req *http.Request) *http.Response

func (f roundTripFunc) RoundTrip(req *http.Request) (*http.Response, error) {

return f(req), nil

}

func httpClientWithRoundTripper(statusCode int, response string) *http.Client {

return &http.Client{

Transport: roundTripFunc(func(req *http.Request) *http.Response {

return &http.Response{

StatusCode: statusCode,

Body: ioutil.NopCloser(bytes.NewBufferString(response)),

}

}),

}

Go internals

Channels https://youtu.be/KBZlN0izeiY Go scheduler https://youtu.be/YHRO5WQGh0k

Setup local Athens for proper go mod

There is a project called Athens for proxying all your go mod downloads. How to use it locally. 1. Create the following files and directories: a. /Users/d.bolgov/.ssh-athens/storage — empty directory to cache go modules b. /Users/d.bolgov/.ssh-athens/.netrc — if you prefer using .netrc

machine github.com
    login [yourlogin]
    password [yourpassword]

machine github.com

password [yourpassword]

c. /Users/d.bolgov/.ssh-athens/gitconfig/.gitconfig — if you want to substitue some urls. I personally …

Installing protobuf tools on MacOS

Installing protoc

brew install protobuf

1	brew install protobuf

Or follow different instructions. Installing grpc_cli Option 1. Easy way.

brew tap grpc/grpc
brew install --with-plugins grpc

1 2	brew tap grpc/grpc brew install --with-plugins grpc

It is described here — https://github.com/grpc/homebrew-grpc. Option 2. Hard way — using cmake and make. NOT RECOMMENDED.

brew install autoconf automake libtool shtool cmake

git clone -b $(curl -L https://grpc.io/release) https://github.com/grpc/grpc
cd grpc
git submodule update --init

mkdir -p cmake/build
cd cmake/build
cmake ../..
make

gRPC_INSTALL=ON make install
# and continue accordgin to https://github.com/grpc/grpc/blob/master/BUILDING.md

brew install autoconf automake libtool shtool cmake

git clone -b $(curl -L https://grpc.io/release) https://github.com/grpc/grpc

cd grpc

git submodule update --init

mkdir -p cmake/build

cd cmake/build

cmake ../..

make

gRPC_INSTALL=ON make install

# and continue accordgin to https://github.com/grpc/grpc/blob/master/BUILDING.md

Or follow these instructions

Nice talk about concurrency in Go

Another good talk. It’s not only about channels, but also about atomics and patterns around ti. https://www.youtube.com/watch?v=YEKjSzIwAdA

Make your bot for telegram using go

It’s really not that difficult. Here are the docs: https://core.telegram.org/bots https://core.telegram.org/bots/api Here is a simple library in go for telegram — https://github.com/go-telegram-bot-api/telegram-bot-api/ (too simple, from my point of view, does not cover all functionality, but okay). And here is a skeletton for making your bots if you want it as just standalone binary — https://github.com/nezorflame/example-telegram-bot/