Build and Test PR

[Repo Assist] Add DateOnly/TimeOnly inference support (`closes #1461`) #341

Sign in to view logs

Triggered via pull request February 22, 2026 15:20

dsyme

synchronize #1609

repo-assist/feature-dateonly-timeonly-1461-03f39b53850547db

Status Failure

Total duration 3m 29s

Artifacts –

pull-requests.yml

on: pull_request

Annotations

20 errors and 20 warnings

Generating expressions works in netstandard2.0 ("Csv

System.Exception : couldn't find a type in type provider with 16 static args

Generating expressions works in netstandard2.0 ("Csv

System.Exception : couldn't find a type in type provider with 16 static args

Generating expressions works in netstandard2.0 ("Csv

System.Exception : couldn't find a type in type provider with 16 static args

Generating expressions works in netstandard2.0 ("Csv

System.Exception : couldn't find a type in type provider with 16 static args

Generating expressions works in netstandard2.0 ("Csv

System.Exception : couldn't find a type in type provider with 16 static args

Generating expressions works in netstandard2.0 ("Csv

System.Exception : couldn't find a type in type provider with 16 static args

Generating expressions works in netstandard2.0 ("Csv

System.Exception : couldn't find a type in type provider with 16 static args

Generating expressions works in netstandard2.0 ("Csv

System.Exception : couldn't find a type in type provider with 16 static args

Generating expressions works in netstandard2.0 ("Csv

System.Exception : couldn't find a type in type provider with 16 static args

Generating expressions works in netstandard2.0 ("Csv

System.Exception : couldn't find a type in type provider with 16 static args

Generating expressions works in netstandard2.0 ("Csv

System.Exception : couldn't find a type in type provider with 16 static args

Generating expressions works in netstandard2.0 ("Csv

System.Exception : couldn't find a type in type provider with 16 static args

Generating expressions works in netstandard2.0 ("Csv

System.Exception : couldn't find a type in type provider with 16 static args

Generating expressions works in netstandard2.0 ("Csv

System.Exception : couldn't find a type in type provider with 16 static args

Generating expressions works in netstandard2.0 ("Csv

System.Exception : couldn't find a type in type provider with 16 static args

Generating expressions works in netstandard2.0 ("Csv

System.Exception : couldn't find a type in type provider with 16 static args

Generating expressions works in netstandard2.0 ("Csv

System.Exception : couldn't find a type in type provider with 16 static args

Can load different nested payloads

Expected: 11/1/2021 But was: 2021-11-01 00:00:00

Can infer tables out of the market depth file

Expected: 1/14/2014 But was: 2014-01-14 00:00:00

Can infer DateTime and DateTimeOffset types correctly

Expected: <System.DateOnly> But was: <System.DateTime>

build-ubuntu

The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.

build-ubuntu

The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.

build-ubuntu

The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.

build-ubuntu

The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.

build-ubuntu: build/build.fs#L250

The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.

build-ubuntu: build/build.fs#L249

The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.

build-ubuntu: build/build.fs#L248

The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.

build-ubuntu: build/build.fs#L247

The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.

build-ubuntu: build/build.fs#L245

The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.

build-ubuntu: build/build.fs#L243

The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.

build-windows

The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.

build-windows

The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.

build-windows

The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.

build-windows

The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.

build-windows: build/build.fs#L250

The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.

build-windows: build/build.fs#L249

The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.

build-windows: build/build.fs#L248

The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.

build-windows: build/build.fs#L247

The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.

build-windows: build/build.fs#L245

The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.

build-windows: build/build.fs#L243

The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.