Skip to content

use tsconfig.src.build.json in rest of libs #35266

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
deyaaeldeen merged 1 commit into from
Jul 22, 2025

use tsconfig.src.build.json in rest of libs

90df61e
Select commit
Loading
Failed to load commit list.
Merged

use tsconfig.src.build.json in rest of libs #35266

use tsconfig.src.build.json in rest of libs
90df61e
Select commit
Loading
Failed to load commit list.
Azure Pipelines / js - pullrequest succeeded Jul 22, 2025 in 34m 54s

Build #20250721.40 had test failures

0 errors / 61 warnings

Details

Tests

  • Failed: 2 (0.00%)
  • Passed: 73,488 (95.57%)
  • Other: 3,405 (4.43%)
  • Total: 76,895

Annotations

Check failure on line 1 in Keys client - create, read, update and delete operations for managed HSM > releaseKey > can import an exportable key and release it

See this annotation in the file changed.

@azure-pipelines azure-pipelines / js - pullrequest

Keys client - create, read, update and delete operations for managed HSM > releaseKey > can import an exportable key and release it 

Unable to find a record for the request PUT https://Sanitized.managedhsm.azure.net/keys/importreleasekey-45725?api-version=7.6 Header differences: Body differences: There are differences between request and recordentry bodies: .release_policy.data: "eyJhbnlPZiI6W3siYWxsT2YiOlt7ImNsYWltIjoic2RrLXRlc3QiLCJlcXVhbHMiOiJ0cnVlIn1dLCJhdXRob3JpdHkiOiJodHRwczovL3Nrcl9hdHRlc3RhdGlvbi5henVyZS5uZXQvIn1dLCJ2ZXJzaW9uIjoiMS4wIn0" != "eyAic2FuaXRpemVkIjogInNhbml0aXplZCIgfQ=="
Raw output 
RecorderError: Unable to find a record for the request PUT https://Sanitized.managedhsm.azure.net/keys/importreleasekey-45725?api-version=7.6
Header differences:
Body differences:
There are differences between request and recordentry bodies:
.release_policy.data: "eyJhbnlPZiI6W3siYWxsT2YiOlt7ImNsYWltIjoic2RrLXRlc3QiLCJlcXVhbHMiOiJ0cnVlIn1dLCJhdXRob3JpdHkiOiJodHRwczovL3Nrcl9hdHRlc3RhdGlvbi5henVyZS5uZXQvIn1dLCJ2ZXJzaW9uIjoiMS4wIn0" != "eyAic2FuaXRpemVkIjogInNhbml0aXplZCIgfQ=="

 ❯ Recorder.handleTestProxyErrors ../../test-utils/recorder/src/recorder.ts:519:13
 ❯ Object.sendRequest ../../test-utils/recorder/src/recorder.ts:545:14
 ❯ Object.sendRequest ../../core/ts-http-runtime/src/policies/redirectPolicy.ts:39:24
 ❯ Object.sendRequest ../../core/ts-http-runtime/src/policies/retryPolicy.ts:57:22
 ❯ Object.sendRequest ../keyvault-common/src/keyVaultAuthenticationPolicy.ts:253:16
 ❯ sendRequest ../../core/ts-http-runtime/src/client/sendRequest.ts:42:22
 ❯ importKey src/generated/src/api/operations.ts:1353:18
 ❯ src/index.ts:494:24
 ❯ Object.withSpan ../../core/core-tracing/src/tracingClient.ts:70:22

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { statusCode: undefined }

Check failure on line 1 in Keys client - create, read, update and delete operations for managed HSM > releaseKey > can update a key's release policy

See this annotation in the file changed.

@azure-pipelines azure-pipelines / js - pullrequest

Keys client - create, read, update and delete operations for managed HSM > releaseKey > can update a key's release policy 

Unable to find a record for the request POST https://Sanitized.managedhsm.azure.net/keys/exportkey-35418/create?api-version=7.6 Header differences: Body differences: There are differences between request and recordentry bodies: .release_policy.data: "eyJhbnlPZiI6W3siYWxsT2YiOlt7ImNsYWltIjoic2RrLXRlc3QiLCJlcXVhbHMiOiJ0cnVlIn1dLCJhdXRob3JpdHkiOiJodHRwczovL3Nrcl9hdHRlc3RhdGlvbi5henVyZS5uZXQvIn1dLCJ2ZXJzaW9uIjoiMS4wIn0" != "eyAic2FuaXRpemVkIjogInNhbml0aXplZCIgfQ=="
Raw output 
RecorderError: Unable to find a record for the request POST https://Sanitized.managedhsm.azure.net/keys/exportkey-35418/create?api-version=7.6
Header differences:
Body differences:
There are differences between request and recordentry bodies:
.release_policy.data: "eyJhbnlPZiI6W3siYWxsT2YiOlt7ImNsYWltIjoic2RrLXRlc3QiLCJlcXVhbHMiOiJ0cnVlIn1dLCJhdXRob3JpdHkiOiJodHRwczovL3Nrcl9hdHRlc3RhdGlvbi5henVyZS5uZXQvIn1dLCJ2ZXJzaW9uIjoiMS4wIn0" != "eyAic2FuaXRpemVkIjogInNhbml0aXplZCIgfQ=="

 ❯ Recorder.handleTestProxyErrors ../../test-utils/recorder/src/recorder.ts:519:13
 ❯ Object.sendRequest ../../test-utils/recorder/src/recorder.ts:545:14
 ❯ Object.sendRequest ../../core/ts-http-runtime/src/policies/redirectPolicy.ts:39:24
 ❯ Object.sendRequest ../../core/ts-http-runtime/src/policies/retryPolicy.ts:57:22
 ❯ Object.sendRequest ../keyvault-common/src/keyVaultAuthenticationPolicy.ts:253:16
 ❯ sendRequest ../../core/ts-http-runtime/src/client/sendRequest.ts:42:22
 ❯ createKey src/generated/src/api/operations.ts:1455:18
 ❯ src/index.ts:322:24
 ❯ Object.withSpan ../../core/core-tracing/src/tracingClient.ts:70:22

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { statusCode: undefined }
View more details on Azure Pipelines
⚡