feat: Use redis v8 instead of v9 for stability reason #1
Annotations
8 errors and 4 warnings
go-test (1.17):
concurrent_buffer.go#L130
cannot use "github.com/go-redis/redis/v8".Z{...} (type "github.com/go-redis/redis/v8".Z) as type *"github.com/go-redis/redis/v8".Z in argument to pipeliner.ZAdd
|
go-test (1.17)
Process completed with exit code 2.
|
go-test (1.18):
concurrent_buffer.go#L130
cannot use redis.Z{…} (value of type "github.com/go-redis/redis/v8".Z) as type *"github.com/go-redis/redis/v8".Z in argument to pipeliner.ZAdd
|
go-test (1.18)
The operation was canceled.
|
go-test (1.20):
concurrent_buffer.go#L130
cannot use redis.Z{…} (value of type "github.com/go-redis/redis/v8".Z) as *"github.com/go-redis/redis/v8".Z value in argument to pipeliner.ZAdd
|
go-test (1.20):
concurrent_buffer.go#L130
cannot use redis.Z{…} (value of type "github.com/go-redis/redis/v8".Z) as *"github.com/go-redis/redis/v8".Z value in argument to pipeliner.ZAdd
|
go-test (1.20)
The operation was canceled.
|
go-test (1.19)
The operation was canceled.
|
go-test (1.17)
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: rrainn/dynamodb-action@v2.0.1. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.
|
go-test (1.18)
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: rrainn/dynamodb-action@v2.0.1. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.
|
go-test (1.20)
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: rrainn/dynamodb-action@v2.0.1. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.
|
go-test (1.19)
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: rrainn/dynamodb-action@v2.0.1. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.
|