Alex Bozhenko
Alex Bozhenko
@thiell what do you think?
> For what is worth we've done it in Cumin (that uses ClusterShell underneath for the transport) and opted to avoid the thousands separator bit as it felt a bit...
Hi @joelshepherd. Do you think you can merge this to enable the countdown feature in the next release?
May be useful: https://github.com/bazelbuild/rules_go/issues/3814
Another thought after looking at https://github.com/golang/go/commit/7aa85e01376d840acc8bb931156d607a00b64a60 Should `go_register_toolchains` just allow to specify `go.env` file? https://github.com/bazelbuild/rules_go/blob/master/go/toolchains.rst#go-register-toolchains Maybe https://github.com/bazelbuild/rules_go/pull/3401 should be further generalized to all go env vars?
@fmeum: https://pkg.go.dev/cmd/go#hdr-Environment_variables lists all possible variables, and it seems like is not just about fetches of dependencies. With standard go toolchain, and go.env file, it is easy to set all...
@AFMiziara FYI should be fixed in https://github.com/bufbuild/protoc-gen-validate/releases/tag/v1.0.2
It is also broken in rules_proto_grpc: https://github.com/rules-proto-grpc/rules_proto_grpc/issues/275
@simonw have you seen https://github.com/erning/gorun ?
@avelino this was created by running stale repos test. Please take a look at description here: https://github.com/avelino/awesome-go/pull/5127