-
Notifications
You must be signed in to change notification settings - Fork 167
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
dotnet emitter crashes and attempts to write a duplicate file name #5218
Comments
Hello @xiangyan99 |
I think it still exists. This was the latest run that was triggered 3 days ago. And here is the log: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4496303&view=logs&j=03afb3bb-7296-55ad-aa07-ceee610c73b2&t=0f320c29-1c90-5304-d2d3-c58a6bb76437&l=606 |
Hello @xiangyan99 In existing sdk code (azure-sdk-for-net/sdk/search/Azure.Search.Documents), there is customized code to rename model Then in the typespec, you define another model To resolve this issue, you need to update the customized code. |
Do you mean client.tsp? I don't see I renamed Did I miss something? |
I mean the customized csharp source code in the azure-sdk-for-net. I passed the code link https://github.com/Azure/azure-sdk-for-net/blob/c7d7ab3eb72a88bd651bb1cba7e269f658f2b7e6/sdk/search/Azure.Search.Documents/src/Indexes/Models/KeywordTokenizer.cs#L9 If you want to keep two models But current azure-rest-api-specs ci pipeline does not honor the temporary changes in azure-sdk-for-net, the ci will always sync the latest commit of azure-sdk-for-net/main to generate code. therefore, the net-automation in azure-rest-api-specs cannot pass. |
I updated the code and removed But it still failed. Any thoughts? @chunyu3 |
As I mentioned above, azure-rest-api-specs ci pipeline will sync the latest commit in azure/azure-sdk-for-net, and generate sdk based on it. Only when the changes of customized code is merged into azure-sdk-for-net, azure-rest-api-specs can see the changes. |
I created PR Azure/azure-rest-api-specs#31462 to migrate Search from swagger to tsp.
The tsp project can be found at https://github.com/Azure/azure-rest-api-specs/tree/search_tsp_preview/specification/search/Azure.Search.
The emitter crashes with error:
System.ArgumentException: An item with the same key has already been added. Key: KeywordTokenizer.cs
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4334521&view=logs&j=03afb3bb-7296-55ad-aa07-ceee610c73b2&t=0f320c29-1c90-5304-d2d3-c58a6bb76437&l=698
We need to identify the blockers for the search TSP migration, and this issue is preventing us from making further progress.
We would appreciate it if you could prioritize it, if possible.
Thank you!
The text was updated successfully, but these errors were encountered: