This updates the flux integration to use the `flux/array` package rather
than directly using the `arrow/array` package.
Flux recently switched to wrapping the array types from arrow and
creating its own array package to be used for table columns instead of
directly referencing the arrow package. This allows us to keep a
consistent interface, but potentially change internal implementations
without changing downstream consumers. Most recently, the
`*array.String` type has some of its own optimizations for certain array
patterns.
This change updates the flux integration to use the new API.
CVE-2020-26160[0] is an access restriction bypass under certain
circumstances when validating audience checks. The original
dgrijalva/jwt-go project is no longer maintained[1] and will not be
issuing a fix for this CVE[2]. Instead, they have transferred ownership
to golang-jwt/jwt[2][3][4].
The following was performed:
1. update chronograf and jsonweb to import golang-jwt/jwt
2. go mod edit -require github.com/golang-jwt/jwt@v3.2.1+incompatible
3. go mod edit -droprequire github.com/dgrijalva/jwt-go
4. go mod tidy
5. make
6. make test
References:
[0] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26160
[1] dgrijalva/jwt-go#462
[2] dgrijalva/jwt-go#463
[3] https://github.com/dgrijalva/jwt-go/blob/master/README.md
[4] https://github.com/golang-jwt/jwt
* build(flux): update flux to v0.123.0
* fix(cmd/influxd/launcher): modify selector aggregate tests to use create empty false
Co-authored-by: Jonathan A. Sternberg <jonathan@influxdata.com>
* build(flux): update flux to v0.122.0
* fix: update group|>last pushdown to choose last row with greatest time
Row order output by group() is not defined, but this change makes the
result consistent with Flux to allow acceptance tests to pass.
* feat(annotations): storage service
* feat: stickers are in db as array
* chore: fix some unintended diffs
* fix: fixes from review
* fix: specific table name for json_each
* fix: update primary keys and constraints
* fix: fix schema
* feat: stream name updates are reflected in annotations via FK
It seems that go-bindata version 3.11.0 was changed and causes issues
when building from a clean Go env.
See :
verifying github.com/kevinburke/go-bindata@v3.11.0+incompatible: checksum mismatch
downloaded: h1:GiPs9jxaG2xY1B5Dt/d/yHUOMlTk14uS35VcmHrdo4I=
go.sum: h1:RcC+GJNmrBHbGaOpQ9MBD8z22rdzlIm0esDRDkyxd4s=
This change updates to the latest go-bindata release.
* Create Dockerfile for running build & release in CI
* Update CircleCI config to use new Docker image
* Update goreleaser to add a linux ARM64 release
William Baker
Jonathan A. Sternberg
Daniel Moran
Jamie Strandboge
Dane Strandboge
Faith Chikwekwe
Christopher M. Wolff
Adrian Thurston
Sean Brickley
Paul Hummer
Nathaniel Cook
davidby-influx
Paul Hummer
Faith Chikwekwe