Repository navigation
[to dev/1.3] cherry pick some fixes from main branch #447
Annotations
15 errors and 5 warnings
|
Build (ubuntu-latest, 1.13)
Process completed with exit code 2.
|
|
Build (ubuntu-latest, 1.13):
client/sessiondataset.go#L129
s.ioTDBRpcDataSet.timeFactor undefined (type *IoTDBRpcDataSet has no field or method timeFactor)
|
|
Build (ubuntu-latest, 1.13):
client/sessiondataset.go#L129
s.ioTDBRpcDataSet.GetCurrentRowTime undefined (type *IoTDBRpcDataSet has no field or method GetCurrentRowTime)
|
|
Build (ubuntu-latest, 1.13):
client/sessiondataset.go#L129
undefined: convertToTimestamp
|
|
Build (ubuntu-latest, stable)
The strategy configuration was canceled because "build.ubuntu-latest_1_13" failed
|
|
Build (ubuntu-latest, stable)
The operation was canceled.
|
|
Build (windows-latest, 1.13)
The strategy configuration was canceled because "build.ubuntu-latest_1_13" failed
|
|
Build (windows-latest, 1.13)
The operation was canceled.
|
|
Build (windows-latest, stable)
The strategy configuration was canceled because "build.ubuntu-latest_1_13" failed
|
|
Build (windows-latest, stable)
The operation was canceled.
|
|
Build (macos-latest, stable)
The strategy configuration was canceled because "build.ubuntu-latest_1_13" failed
|
|
Build (macos-latest, stable)
The operation was canceled.
|
|
Build (macos-latest, stable):
client/sessiondataset.go#L129
s.ioTDBRpcDataSet.timeFactor undefined (type *IoTDBRpcDataSet has no field or method timeFactor)
|
|
Build (macos-latest, stable):
client/sessiondataset.go#L129
s.ioTDBRpcDataSet.GetCurrentRowTime undefined (type *IoTDBRpcDataSet has no field or method GetCurrentRowTime)
|
|
Build (macos-latest, stable):
client/sessiondataset.go#L129
undefined: convertToTimestamp
|
|
Build (ubuntu-latest, 1.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. 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/
|
|
Build (ubuntu-latest, stable)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build (windows-latest, 1.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build (windows-latest, stable)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build (macos-latest, stable)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|