Fix RpcDataSet deadlock, timezone compatibility, column index issues,… #147
Annotations
34 warnings
|
build (macos-latest)
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-dotnet@v4. 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):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L63
Field 'RpcDataSet._timeFactor' is never assigned to, and will always have its default value 0
|
|
build (macos-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L64
Field 'RpcDataSet._timePrecision' is never assigned to, and will always have its default value null
|
|
build (macos-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L64
Field 'RpcDataSet._timePrecision' is never assigned to, and will always have its default value null
|
|
build (macos-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L63
Field 'RpcDataSet._timeFactor' is never assigned to, and will always have its default value 0
|
|
build (macos-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L63
Field 'RpcDataSet._timeFactor' is never assigned to, and will always have its default value 0
|
|
build (macos-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L64
Field 'RpcDataSet._timePrecision' is never assigned to, and will always have its default value null
|
|
build (macos-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L64
Field 'RpcDataSet._timePrecision' is never assigned to, and will always have its default value null
|
|
build (macos-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L63
Field 'RpcDataSet._timeFactor' is never assigned to, and will always have its default value 0
|
|
build (macos-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L63
Field 'RpcDataSet._timeFactor' is never assigned to, and will always have its default value 0
|
|
build (macos-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L64
Field 'RpcDataSet._timePrecision' is never assigned to, and will always have its default value null
|
|
build (ubuntu-latest)
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-dotnet@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 (ubuntu-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L64
Field 'RpcDataSet._timePrecision' is never assigned to, and will always have its default value null
|
|
build (ubuntu-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L63
Field 'RpcDataSet._timeFactor' is never assigned to, and will always have its default value 0
|
|
build (ubuntu-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L64
Field 'RpcDataSet._timePrecision' is never assigned to, and will always have its default value null
|
|
build (ubuntu-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L63
Field 'RpcDataSet._timeFactor' is never assigned to, and will always have its default value 0
|
|
build (ubuntu-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L63
Field 'RpcDataSet._timeFactor' is never assigned to, and will always have its default value 0
|
|
build (ubuntu-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L64
Field 'RpcDataSet._timePrecision' is never assigned to, and will always have its default value null
|
|
build (ubuntu-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L63
Field 'RpcDataSet._timeFactor' is never assigned to, and will always have its default value 0
|
|
build (ubuntu-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L64
Field 'RpcDataSet._timePrecision' is never assigned to, and will always have its default value null
|
|
build (ubuntu-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L64
Field 'RpcDataSet._timePrecision' is never assigned to, and will always have its default value null
|
|
build (ubuntu-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L63
Field 'RpcDataSet._timeFactor' is never assigned to, and will always have its default value 0
|
|
build (ubuntu-latest)
Restore cache failed: Some specified paths were not resolved, unable to cache dependencies.
|
|
build (windows-latest)
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-dotnet@v4. 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):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L63
Field 'RpcDataSet._timeFactor' is never assigned to, and will always have its default value 0
|
|
build (windows-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L64
Field 'RpcDataSet._timePrecision' is never assigned to, and will always have its default value null
|
|
build (windows-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L63
Field 'RpcDataSet._timeFactor' is never assigned to, and will always have its default value 0
|
|
build (windows-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L64
Field 'RpcDataSet._timePrecision' is never assigned to, and will always have its default value null
|
|
build (windows-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L64
Field 'RpcDataSet._timePrecision' is never assigned to, and will always have its default value null
|
|
build (windows-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L64
Field 'RpcDataSet._timePrecision' is never assigned to, and will always have its default value null
|
|
build (windows-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L63
Field 'RpcDataSet._timeFactor' is never assigned to, and will always have its default value 0
|
|
build (windows-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L63
Field 'RpcDataSet._timeFactor' is never assigned to, and will always have its default value 0
|
|
build (windows-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L63
Field 'RpcDataSet._timeFactor' is never assigned to, and will always have its default value 0
|
|
build (windows-latest):
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L64
Field 'RpcDataSet._timePrecision' is never assigned to, and will always have its default value null
|