Fix RpcDataSet deadlock, timezone compatibility, column index issues, and deprecation cleanup #146
Annotations
11 warnings
|
Build:
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L64
Field 'RpcDataSet._timePrecision' is never assigned to, and will always have its default value null
|
|
Build:
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L63
Field 'RpcDataSet._timeFactor' is never assigned to, and will always have its default value 0
|
|
Build:
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L63
Field 'RpcDataSet._timeFactor' is never assigned to, and will always have its default value 0
|
|
Build:
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L64
Field 'RpcDataSet._timePrecision' is never assigned to, and will always have its default value null
|
|
Build:
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L63
Field 'RpcDataSet._timeFactor' is never assigned to, and will always have its default value 0
|
|
Build:
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L64
Field 'RpcDataSet._timePrecision' is never assigned to, and will always have its default value null
|
|
Build:
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L64
Field 'RpcDataSet._timePrecision' is never assigned to, and will always have its default value null
|
|
Build:
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L63
Field 'RpcDataSet._timeFactor' is never assigned to, and will always have its default value 0
|
|
Build:
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L63
Field 'RpcDataSet._timeFactor' is never assigned to, and will always have its default value 0
|
|
Build:
src/Apache.IoTDB/DataStructure/RpcDataSet.cs#L64
Field 'RpcDataSet._timePrecision' is never assigned to, and will always have its default value null
|
|
Check License Header
Restore cache failed: Some specified paths were not resolved, unable to cache dependencies.
|
Loading