Fix DateTimeKind collisions in dictionary encoding and mark INT96 DateTimeKind as Unspecified - #695
Closed
Kuinox wants to merge 2 commits into
Closed
Fix DateTimeKind collisions in dictionary encoding and mark INT96 DateTimeKind as Unspecified#695Kuinox wants to merge 2 commits into
Kuinox wants to merge 2 commits into
Annotations
7 errors and 11 warnings
|
|
|
src/Parquet.Test/Types/EndToEndDateTimeKindTest.cs#L27
'DataColumn?' does not contain a definition for 'Data' and no accessible extension method 'Data' accepting a first argument of type 'DataColumn?' could be found (are you missing a using directive or an assembly reference?)
|
|
src/Parquet.Test/Types/EndToEndDateTimeKindTest.cs#L24
The type or namespace name 'DataColumn' could not be found (are you missing a using directive or an assembly reference?)
|
|
src/Parquet.Test/Types/EndToEndDateTimeKindTest.cs#L23
The type or namespace name 'DataColumn' could not be found (are you missing a using directive or an assembly reference?)
|
|
src/Parquet.Test/Types/EndToEndDateTimeKindTest.cs#L27
'DataColumn?' does not contain a definition for 'Data' and no accessible extension method 'Data' accepting a first argument of type 'DataColumn?' could be found (are you missing a using directive or an assembly reference?)
|
|
src/Parquet.Test/Types/EndToEndDateTimeKindTest.cs#L24
The type or namespace name 'DataColumn' could not be found (are you missing a using directive or an assembly reference?)
|
|
src/Parquet.Test/Types/EndToEndDateTimeKindTest.cs#L23
The type or namespace name 'DataColumn' could not be found (are you missing a using directive or an assembly reference?)
|
|
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. 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/
|
|
src/Parquet.PerfRunner/Benchmarks/EncodingBenchmarks.cs#L62
Dereference of a possibly null reference.
|
|
src/Parquet.PerfRunner/Benchmarks/EncodingBenchmarks.cs#L62
Dereference of a possibly null reference.
|
|
src/Parquet.PerfRunner/Benchmarks/Curiosities.cs#L18
Non-nullable field '_ints' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
|
|
src/Parquet.Test/Serialisation/ParquetSerializerTest.cs#L1318
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
src/Parquet.Test/ParquetWriterTest.cs#L121
Cannot convert null literal to non-nullable reference type.
|
|
src/Parquet.PerfRunner/Benchmarks/EncodingBenchmarks.cs#L67
Dereference of a possibly null reference.
|
|
src/Parquet.PerfRunner/Benchmarks/EncodingBenchmarks.cs#L67
Dereference of a possibly null reference.
|
|
src/Parquet.PerfRunner/Benchmarks/EncodingBenchmarks.cs#L62
Dereference of a possibly null reference.
|
|
src/Parquet.PerfRunner/Benchmarks/EncodingBenchmarks.cs#L62
Dereference of a possibly null reference.
|
|
src/Parquet.PerfRunner/Benchmarks/Curiosities.cs#L18
Non-nullable field '_ints' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
|
The logs for this run have expired and are no longer available.
Loading