[PECOBLR-1384] Complete telemetry implementation: Phases 8-10 #775
Annotations
20 errors and 4 warnings
|
Test and Build (1.20.x, ubuntu-latest):
connection_test.go#L1082
too many arguments in call to testConn.runQuery
|
|
Test and Build (1.20.x, ubuntu-latest):
connection_test.go#L1040
too many arguments in call to testConn.runQuery
|
|
Test and Build (1.20.x, ubuntu-latest):
connection_test.go#L1386
too many arguments in call to testConn.runQuery
|
|
Test and Build (1.20.x, ubuntu-latest):
connection_test.go#L1333
too many arguments in call to testConn.runQuery
|
|
Test and Build (1.20.x, ubuntu-latest):
connection_test.go#L1280
too many arguments in call to testConn.runQuery
|
|
Test and Build (1.20.x, ubuntu-latest):
connection_test.go#L1228
too many arguments in call to testConn.runQuery
|
|
Test and Build (1.20.x, ubuntu-latest):
connection_test.go#L1175
too many arguments in call to testConn.runQuery
|
|
Test and Build (1.20.x, ubuntu-latest):
connection_test.go#L1128
too many arguments in call to testConn.runQuery
|
|
Test and Build (1.20.x, ubuntu-latest):
connection_test.go#L1082
too many arguments in call to testConn.runQuery
|
|
Test and Build (1.20.x, ubuntu-latest):
connection_test.go#L1040
too many arguments in call to testConn.runQuery
|
|
Lint:
telemetry/benchmark_test.go#L148
Error return value of `mgr.releaseClient` is not checked (errcheck)
|
|
Lint:
connection_test.go#L1386
too many arguments in call to testConn.runQuery
|
|
Lint:
connection_test.go#L1333
too many arguments in call to testConn.runQuery
|
|
Lint:
connection_test.go#L1280
too many arguments in call to testConn.runQuery
|
|
Lint:
connection_test.go#L1228
too many arguments in call to testConn.runQuery
|
|
Lint:
connection_test.go#L1175
too many arguments in call to testConn.runQuery
|
|
Lint:
connection_test.go#L1128
too many arguments in call to testConn.runQuery
|
|
Lint:
connection_test.go#L1082
too many arguments in call to testConn.runQuery
|
|
Lint:
connection_test.go#L1040
too many arguments in call to testConn.runQuery
|
|
Lint:
connection.go#L1
: # github.com/databricks/databricks-sql-go [github.com/databricks/databricks-sql-go.test]
|
|
Test and Build (1.20.x, ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff, golangci/golangci-lint-action@d6238b002a20823d52840fda27e2d4891c5952dc. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Lint
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0SKXTaQAAAAA/ne7eTAn1QZSB1VxdRVtERE0yRURHRTA4MjAARWRnZQ==
|
|
Lint
Failed to restore: Cache service responded with 400
|