Somewhat proper standalone timer implementation #302
FrankvdStamAnnotations
1 error and 7 warnings
|
Build
Process completed with exit code 1.
|
|
Build
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/[email protected], actions/setup-dotnet@v3, actions/setup-java@v2, actions/cache@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: actions/[email protected], actions/setup-java@v2, actions/cache@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
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Build
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Build:
tests/SoulMemory.Tests/Mocks/ProcessHookMock.cs#L27
Non-nullable property 'ProcessWrapper' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Build:
tests/SoulMemory.Tests/Mocks/ProcessHookMock.cs#L110
The event 'ProcessHookMock.Exited' is never used
|
|
Build:
tests/SoulMemory.Tests/Mocks/ProcessHookMock.cs#L109
The event 'ProcessHookMock.Hooked' is never used
|