Skip to content

Disable Semaphore and fix some flaky tests (#157) #150

Disable Semaphore and fix some flaky tests (#157)

Disable Semaphore and fix some flaky tests (#157) #150

Triggered via push August 29, 2024 20:25
Status Success
Total duration 4m 39s
Artifacts 1

publish.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

18 warnings
nuget
The following actions uses node12 which is deprecated and will be forced to run on node16: web3j/substr-action@v1.2, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
nuget
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, web3j/substr-action@v1.2, actions/setup-dotnet@v3, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
nuget: src/CommonLib/LdapConnectionPool.cs#L22
Field 'LdapConnectionPool._semaphore' is never assigned to, and will always have its default value null
nuget
The `set-output` 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/
nuget
ProjectReference 'D:\a\SharpHoundCommon\SharpHoundCommon\src\CommonLib\SharpHoundCommonLib.csproj' was resolved using '.NETFramework,Version=v4.6.2' instead of the project target framework '.NETCoreApp,Version=v7.0'. This project may not be fully compatible with your project.
nuget
ProjectReference 'D:\a\SharpHoundCommon\SharpHoundCommon\src\SharpHoundRPC\SharpHoundRPC.csproj' was resolved using '.NETFramework,Version=v4.6.2' instead of the project target framework '.NETCoreApp,Version=v7.0'. This project may not be fully compatible with your project.
nuget: src/CommonLib/LdapConnectionPool.cs#L22
Field 'LdapConnectionPool._semaphore' is never assigned to, and will always have its default value null
nuget: test/unit/ComputerSessionProcessorTest.cs#L215
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.
nuget: test/unit/ComputerSessionProcessorTest.cs#L234
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.
nuget: test/unit/AsyncEnumerableTests.cs#L79
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.
nuget: test/unit/AsyncEnumerableTests.cs#L89
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.
nuget: test/unit/UserRightsAssignmentProcessorTest.cs#L81
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.
nuget: test/unit/LocalGroupProcessorTest.cs#L129
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.
nuget: test/unit/LdapPropertyTests.cs#L960
This call site is reachable on all platforms. 'SecurityIdentifier' is only supported on: 'windows'. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1416)
ghpages
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/download-artifact@v2, JamesIves/github-pages-deploy-action@4.1.4. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
ghpages
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/download-artifact@v2, JamesIves/github-pages-deploy-action@4.1.4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ghpages
The `set-output` 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/
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "report". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

Artifacts

Produced during runtime
Name Size
report Expired
8.47 MB