Skip to content
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.

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

Failed to build SDK due to the failure when building @azure/core-rest-pipeline #31998

Open
wanlwanl opened this issue Nov 29, 2024 · 5 comments
Assignees
Labels
Azure.Core Client This issue points to a problem in the data-plane of the library. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team

Comments

@wanlwanl
Copy link
Member

Describe the bug
Got the following error on building @azure/core-rest-pipeline when generating SDK in Azure/azure-rest-api-specs#31549:

08:30:43.552 cmdout 	[automation_generate.sh] src/util/file.ts(119,10): error TS2352: Conversion of type '{ type: string; lastModified: number; webkitRelativePath: string; size: number; name: string; stream: () => ReadableStream<Uint8Array<ArrayBufferLike>>; [rawContent]: () => ReadableStream<Uint8Array> | NodeJS.ReadableStream; arrayBuffer: () => never; slice: () => never; text: () => never; }' to type 'File & RawContent' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.

To Reproduce
Steps to reproduce the behavior:

  1. create a PR as Adding interactive types to Advanced messaging azure-rest-api-specs#31549

Expected behavior
JS SDK automation in PR of Azure/azure-rest-api-specs repo should succeed.

Additional context

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4368499&view=logs&j=47092895-c7c8-567a-c7a6-8c88f3ec178e&t=d293a8e8-c6af-5091-cdf7-4c66482dd6f2&l=2220

@github-actions github-actions bot added Azure.Core Client This issue points to a problem in the data-plane of the library. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team labels Nov 29, 2024
Copy link

Copy link

Thank you for your feedback. Tagging and routing to the team member best able to assist.

@kazrael2119
Copy link
Contributor

kazrael2119 commented Nov 29, 2024

I encountered the same issue in my pr of sdk repo, here is the log: https://dev.azure.com/azure-sdk/public/_build/results?buildId=4361393&view=logs&j=3dc8fd7e-4368-5a92-293e-d53cefc8c4b3&t=6b39eeeb-8630-577b-6174-f2bee8ec791c&l=483

and my solution is to delete common/config/rush/pnpm-lock.yaml file and common\temp folder locally first, then re-run rush update and build the package. But I don't know how to fix this issue in JS SDK automation

@jeremymeng
Copy link
Member

This may be fixed by PR #31990

@jeremymeng jeremymeng assigned jeremymeng and unassigned timovv Dec 2, 2024
@jeremymeng
Copy link
Member

This was due to tshy pulling in typescript 5.7.2 which contains changes to lib.dom.d.ts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Azure.Core Client This issue points to a problem in the data-plane of the library. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team
Projects
None yet
Development

No branches or pull requests

4 participants