Skip to content

Memoized hydrate calls underlying function names are incorrectly resolved #897

Memoized hydrate calls underlying function names are incorrectly resolved

Memoized hydrate calls underlying function names are incorrectly resolved #897

Re-run triggered February 1, 2024 17:22
Status Failure
Total duration 24s
Artifacts

acceptance-test.yml

on: pull_request
Run chaos acceptance tests
0s
Run chaos acceptance tests
Fit to window
Zoom out
Zoom in

Annotations

15 errors and 1 warning
Build: plugin/get_source_files.go#L7
missing go.sum entry for module providing package github.com/turbot/go-kit/files (imported by github.com/turbot/steampipe-plugin-sdk/v5/getter); to add:
Build: plugin/connection_data.go#L11
missing go.sum entry for module providing package github.com/turbot/go-kit/filewatcher (imported by github.com/turbot/steampipe-plugin-sdk/v5/plugin); to add:
Build: plugin/column.go#L7
missing go.sum entry for module providing package github.com/turbot/go-kit/helpers (imported by github.com/turbot/steampipe-plugin-sdk/v5/grpc); to add:
Build: plugin/column.go#L8
missing go.sum entry for module providing package github.com/turbot/go-kit/types (imported by github.com/turbot/steampipe-plugin-sdk/v5/grpc/proto); to add:
Build
Process completed with exit code 1.
Build: grpc/shared/interface.go#L55
undefined: plugin (typecheck)
Build: grpc/shared/interface.go#L14
undefined: plugin (typecheck)
Build: grpc/shared/interface.go#L61
undefined: plugin (typecheck)
Build: grpc/quals.go#L8
"time" imported and not used (typecheck)
Build: getter/get_files.go#L69
undefined: getter (typecheck)
Build: getter/get_files.go#L71
undefined: getter (typecheck)
Build: plugin/table_fetch.go#L154
missing type in composite literal (typecheck)
Build: plugin/table_fetch.go#L463
missing type in composite literal (typecheck)
Build
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: golangci/golangci-lint-action@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.