Skip to content

chore: upload artifacts update to v4 (#164) #152

chore: upload artifacts update to v4 (#164)

chore: upload artifacts update to v4 (#164) #152

Triggered via push September 17, 2024 19:24
Status Failure
Total duration 4m 11s
Artifacts 1

publish.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

1 error and 14 warnings
ghpages
This request has been automatically failed because it uses a deprecated version of `actions/download-artifact: v2`. Learn more: https://github.blog/changelog/2024-02-13-deprecation-notice-v1-and-v2-of-the-artifact-actions/
nuget
The following actions uses node12 which is deprecated and will be forced to run on node16: web3j/[email protected]. 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/[email protected], actions/setup-dotnet@v3. 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/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/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/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/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)

Artifacts

Produced during runtime
Name Size
report
975 KB