wip: ldap utils tests #893
Annotations
10 errors and 11 warnings
build:
test/unit/LDAPUtilsTest.cs#L85
'LdapUtils' does not contain a definition for 'GetForest' and no accessible extension method 'GetForest' accepting a first argument of type 'LdapUtils' could be found (are you missing a using directive or an assembly reference?)
|
build:
test/unit/LDAPUtilsTest.cs#L97
Argument 1 must be passed with the 'out' keyword
|
build:
test/unit/LDAPUtilsTest.cs#L99
'LdapUtils' does not contain a definition for 'BuildLdapPath' and no accessible extension method 'BuildLdapPath' accepting a first argument of type 'LdapUtils' could be found (are you missing a using directive or an assembly reference?)
|
build:
test/unit/LDAPUtilsTest.cs#L108
Argument 1 must be passed with the 'out' keyword
|
build:
test/unit/LDAPUtilsTest.cs#L110
'LdapUtils' does not contain a definition for 'BuildLdapPath' and no accessible extension method 'BuildLdapPath' accepting a first argument of type 'LdapUtils' could be found (are you missing a using directive or an assembly reference?)
|
build:
test/unit/LDAPUtilsTest.cs#L85
'LdapUtils' does not contain a definition for 'GetForest' and no accessible extension method 'GetForest' accepting a first argument of type 'LdapUtils' could be found (are you missing a using directive or an assembly reference?)
|
build:
test/unit/LDAPUtilsTest.cs#L97
Argument 1 must be passed with the 'out' keyword
|
build:
test/unit/LDAPUtilsTest.cs#L99
'LdapUtils' does not contain a definition for 'BuildLdapPath' and no accessible extension method 'BuildLdapPath' accepting a first argument of type 'LdapUtils' could be found (are you missing a using directive or an assembly reference?)
|
build:
test/unit/LDAPUtilsTest.cs#L108
Argument 1 must be passed with the 'out' keyword
|
build:
test/unit/LDAPUtilsTest.cs#L110
'LdapUtils' does not contain a definition for 'BuildLdapPath' and no accessible extension method 'BuildLdapPath' accepting a first argument of type 'LdapUtils' could be found (are you missing a using directive or an assembly reference?)
|
build
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, 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/
|
build
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.
|
build
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.
|
build:
test/unit/GroupProcessorTest.cs#L48
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:
test/unit/GroupProcessorTest.cs#L55
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:
test/unit/GroupProcessorTest.cs#L62
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:
test/unit/Facades/MockSearchResultEntry.cs#L30
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:
test/unit/ACLProcessorTest.cs#L724
The variable 'expectedRightName' is assigned but its value is never used
|
build:
test/unit/ACLProcessorTest.cs#L831
The variable 'expectedRightName' is assigned but its value is never used
|
build:
test/unit/ACLProcessorTest.cs#L896
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:
test/unit/ACLProcessorTest.cs#L905
The variable 'expectedRightName' is assigned but its value is never used
|