[EXPERIMENTAL] NATS protocol parser #1197
Annotations
9 warnings
|
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Build:
sandbox/MicroBenchmark/NatsProtoParserBench.cs#L12
Non-nullable field '_sequences' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
|
Build:
sandbox/MicroBenchmark/NatsProtoParserBench.cs#L13
Non-nullable field '_parser' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
|
Build:
NatsProtocolParserProf/Program.cs#L23
Non-nullable field '_sequences' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
|
Build:
NatsProtocolParserProf/Program.cs#L24
Non-nullable field '_parser' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
|
Build:
sandbox/MicroBenchmark/NatsProtoParserBench.cs#L12
Non-nullable field '_sequences' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
|
Build:
sandbox/MicroBenchmark/NatsProtoParserBench.cs#L13
Non-nullable field '_parser' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
|
Build:
NatsProtocolParserProf/Program.cs#L23
Non-nullable field '_sequences' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
|
Build:
NatsProtocolParserProf/Program.cs#L24
Non-nullable field '_parser' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
Loading