Changing the handling of client claims to use JSON (#4886) #195
trwalkebenchmark-action.yml
on: push
Run performance benchmarks
7m 22s
Annotations
4 warnings
|
Run performance benchmarks
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/setup-dotnet@3447fd6a9f9e57506b15f895c5b76d3b197dc7c2, actions/cache@e12d46a63a90f2fae62d114769bbf2a179198b5c. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Run performance benchmarks:
src/client/Microsoft.Identity.Client/ApiConfig/AcquireTokenByUsernameAndPasswordConfidentialParameterBuilder.cs#L21
XML comment has cref attribute 'AcquireTokenByUsernamePassword(IEnumerable{string}, string, string)' that could not be resolved
|
|
Run performance benchmarks:
src/client/Microsoft.Identity.Client/ApiConfig/AcquireTokenByUsernameAndPasswordConfidentialParameterBuilder.cs#L21
XML comment has cref attribute 'AcquireTokenByUsernamePassword(IEnumerable{string}, string, string)' that could not be resolved
|
|
Run performance benchmarks:
tests/Microsoft.Identity.Test.Common/Core/Mocks/MockHttpMessageHandler.cs#L68
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.
|