F5
F5
```log [email protected]/handler.go:44 otel err: rpc error: code = Internal desc = grpc: error while marshaling: string field contains invalid UTF-8 go.opentelemetry.io/otel.(*delegator).Handle /go/pkg/mod/go.opentelemetry.io/[email protected]/handler.go:44 go.opentelemetry.io/otel.Handle /go/pkg/mod/go.opentelemetry.io/[email protected]/handler.go:97 go.opentelemetry.io/otel/sdk/trace.(*batchSpanProcessor).processQueue /go/pkg/mod/go.opentelemetry.io/otel/[email protected]/trace/batch_span_processor.go:299 go.opentelemetry.io/otel/sdk/trace.NewBatchSpanProcessor.func1 /go/pkg/mod/go.opentelemetry.io/otel/[email protected]/trace/batch_span_processor.go:125 ``` According...
The command line is more concise for simple scenarios. Like this: ```sh air --build='./cmd/app' --args='start --config /path/file' ```
https://github.com/fullstorydev/grpcurl/blob/f1d396c31eda34a8b546fae7e547742b8acf0f6c/Dockerfile#L22 Suggest use alpine as base image instead of scratch.
tree: ```text . ├── base │ ├── kafka.yaml │ └── kustomization.yaml └── overlays ├── kustomization.yaml ├── output.yaml └── patch.yaml ``` base content: ```yaml # kustomization.yaml resources: - kafka.yaml # kafka.yaml...
# current The goimports will retain blank lines and multiple groups will exist after formatting. testdata in.go: ```go import ( "fmt" "github.com/foo/a" "github.com/foo/b" "go.pkg.com/bar/x" "go.pkg.com/bar/y" "context" "github.com/foo/c" "go.pkg.com/bar/z" ) ```...
Updates golang/go#64271
https://github.com/mroth/weightedrand/blob/82b9ec74aca51314533f5ad81822c7b722021e58/weightedrand.go#L41-L44 Sort doesn't make any sense for randomness. And it will change the order of the original array, which is not a good practice.