better error handling in http broadcasts ; remove blocking behavior from MoveNextAsync()
#246
Annotations
1 error and 9 warnings
|
|
|
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
src/DemoFile.Benchmark/DemoParserBenchmark.cs#L25
Non-nullable field '_fileStream' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
|
|
src/DemoFile.Benchmark/DemoParserBenchmark.cs#L26
Non-nullable field '_demoBytes' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
|
|
src/DemoFile.Test/Integration/HttpBroadcastReaderTest.cs#L46
Dereference of a possibly null reference.
|
|
src/DemoFile.Benchmark/DemoParserBenchmark.cs#L25
Non-nullable field '_fileStream' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
|
|
src/DemoFile.Benchmark/DemoParserBenchmark.cs#L26
Non-nullable field '_demoBytes' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
|
|
src/DemoFile.Test/Integration/HttpBroadcastReaderTest.cs#L46
Dereference of a possibly null reference.
|
|
src/DemoFile.Benchmark/DemoParserBenchmark.cs#L25
Non-nullable field '_fileStream' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
|
|
src/DemoFile.Benchmark/DemoParserBenchmark.cs#L26
Non-nullable field '_demoBytes' 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