You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since go1.15, there's a new vet check for code such as string(x) where x has an integer type other than rune.
This vet check is enabled by default on go test. https://golang.org/doc/go1.15#vet
To Reproduce
Steps to reproduce the behavior:
use go v1.15
go test ./pkg/chunkenc/
Expected behavior
tests pass
Environment:
go v1.15
linux
Screenshots, Promtail config, or terminal output
aurelien-> go test ./pkg/chunkenc/
# github.com/grafana/loki/pkg/chunkenc
pkg/chunkenc/memchunk_test.go:258:59: conversion from int to string yields a string of one rune, not a string of digits (did you mean fmt.Sprint(x)?)
pkg/chunkenc/memchunk_test.go:274:22: conversion from int to string yields a string of one rune, not a string of digits (did you mean fmt.Sprint(x)?)
FAIL github.com/grafana/loki/pkg/chunkenc [build failed]
FAIL
The text was updated successfully, but these errors were encountered:
Since go1.15, there's a new vet check for code such as string(x) where x
has an integer type other than rune. This vet check is enabled by
default on go test.
TestSerialization failed because of that, this commit replaces `string()`
conversions with `strconv.Itoa` calls
Fixesgrafana#2646
Since go1.15, there's a new vet check for code such as string(x) where x
has an integer type other than rune. This vet check is enabled by
default on go test.
TestSerialization failed because of that, this commit replaces `string()`
conversions with `strconv.Itoa` calls
Fixes#2646
Describe the bug
Since go1.15, there's a new vet check for code such as
string(x)
where x has an integer type other thanrune
.This vet check is enabled by default on
go test
. https://golang.org/doc/go1.15#vetTo Reproduce
Steps to reproduce the behavior:
go test ./pkg/chunkenc/
Expected behavior
tests pass
Environment:
Screenshots, Promtail config, or terminal output
The text was updated successfully, but these errors were encountered: