If you've ever dealt with a team where different people had different versions of linters installed, you'll quickly realize that you should also lock your tools.
Before Go 1.13 the recommended solution was to use tools.go file like this:
// +build tools
package tools
import (
So, are you building microservices? Take a look at a few of these symptoms, and decide for yourself:
We have a s3cr3t repository (ok, you can probably find it, but don't peek) that we will announce right before the contest start. It's some of the exercises that were literally and liberally stolen from literally and liberally stolen from the Exercism.io Go track.
Fork this repo, solve the exercises, and submit a pull request TO THAT REPO, NOT EXERCISM/GO for judging with the description containing your personal Tally (see rubric). No more commits after the time limit, but you can fuss with your Pull Request more after the time is up (like counting your score).
Please notify the judges in Slack the #go-contest channel which one, if any of your fully 100% passing solutions, should be considered for Special Awards:
"github.com/julienschmidt/httprouter"
https://marcofranssen.nl/improved-graceful-shutdown-webserver/
https://github.com/julienschmidt/httprouter
package main
import (
| package log | |
| import ( | |
| "fmt" | |
| gokitlog "github.com/go-kit/kit/log" | |
| "github.com/sirupsen/logrus" | |
| stackdriver "github.com/icco/logrus-stackdriver-formatter" | |
| ) |
| package echomw | |
| import ( | |
| "time" | |
| "github.com/labstack/echo" | |
| "go.uber.org/zap" | |
| "go.uber.org/zap/zapcore" | |
| ) |
| // keepDoingSomething will keep trying to doSomething() until either | |
| // we get a result from doSomething() or the timeout expires | |
| func keepDoingSomething() (bool, error) { | |
| timeout := time.After(5 * time.Second) | |
| tick := time.Tick(500 * time.Millisecond) | |
| // Keep trying until we're timed out or got a result or got an error | |
| for { | |
| select { | |
| // Got a timeout! fail with a timeout error | |
| case <-timeout: |
From Apache Arrow Git Tips I’m used to working with git merge and this has made life difficult for me when working with Apache Arrow because it doesn’t use a merge model and pull request branches often need to rebased against master and force pushed.
There are numerous ways to work in this model but this article documents the approach I use, based on some guidance I was given on one of my PRs. I’m documenting this for my own benefit but hopefully it helps others too.
When you first fork the repo, you need to set up the upstream apache git repo as a remote. I prefer to name this remote apache rather than upstream since it is more explicit, especially if I add other remotes (such as other contributors forks).
Cloning the repo using one of the below techniques should correctly but you may still getting an unrecognized import error.
As it stands for Go v1.13, I found in the doc that we should use the GOPRIVATE variable like so:
GOPRIVATE=github.com/ORGANISATION_OR_USER_NAME go get -u -f github.com/ORGANISATION_OR_USER_NAME/REPO_NAME
The 'go env -w' command (see 'go help env') can be used to set these variables for future go command invocations.
go get private repos using SSH key auth instead of password auth.