Merge pull request #927 from warrenbuckley/dependabot/npm_and_yarn/Lo… #591
Annotations
12 warnings
build
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v3, microsoft/vs-intellicode@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
build
The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/vs-intellicode@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
build:
LogViewer.Server/Models/LogResults.cs#L7
Non-nullable property 'Logs' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
build:
LogViewer.Server/Models/LogResults.cs#L9
Non-nullable property 'MessageTemplates' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
build:
LogViewer.Server/Parser/LogParser.cs#L82
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
|
build:
LogViewer.Server/Parser/LogParser.cs#L72
Possible null reference assignment.
|
build:
LogViewer.Server/Parser/LogParser.cs#L77
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
build:
LogViewer.Server/Models/LogResults.cs#L7
Non-nullable property 'Logs' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
build:
LogViewer.Server/Models/LogResults.cs#L9
Non-nullable property 'MessageTemplates' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
build:
LogViewer.Server/Parser/LogParser.cs#L82
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
|
build:
LogViewer.Server/Parser/LogParser.cs#L72
Possible null reference assignment.
|
build:
LogViewer.Server/Parser/LogParser.cs#L77
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|