You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
error ambiguous-symbol: "nextLink" is an ambiguous name between TypeSpec.nextLink, Azure.Core.nextLink. Try using fully qualified name instead: TypeSpec.nextLink, Azure.Core.nextLink
07:37:50.276 cmderr E [Go] [ERROR] total 2 error(s):
07:37:50.276 cmderr E [Go] [ERROR] failed to execute `tsp-client init --tsp-config /mnt/vss/_work/1/s/azure-rest-api-specs/specification/azurefleet/AzureFleet.Management/tspconfig.yaml --commit 19eb9ac21c5b3b292f64a17e55985b8690f5e7c3 --repo Azure/azure-rest-api-specs --local-spec-repo /mnt/vss/_work/1/s/azure-rest-api-specs/specification/azurefleet/AzureFleet.Management --emitter-options module-version=0.1.0 --debug`
07:37:50.276 cmderr E [Go] [ERROR] /mnt/vss/_work/1/s/azure-sdk-for-go/src/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/computefleet/armcomputefleet/TempTypeSpecFiles/AzureFleet.Management/virtualMachineScaleSet.tsp:60:4 - error ambiguous-symbol: "nextLink" is an ambiguous name between TypeSpec.nextLink, Azure.Core.nextLink. Try using fully qualified name instead: TypeSpec.nextLink, Azure.Core.nextLink
07:37:50.276 cmderr E [Go] [ERROR] failed to execute `tsp-client init --tsp-config /mnt/vss/_work/1/s/azure-rest-api-specs/specification/fabric/Microsoft.Fabric.Management/tspconfig.yaml --commit 19eb9ac21c5b3b292f64a17e55985b8690f5e7c3 --repo Azure/azure-rest-api-specs --local-spec-repo /mnt/vss/_work/1/s/azure-rest-api-specs/specification/fabric/Microsoft.Fabric.Management --emitter-options module-version=0.1.0 --debug`
07:37:50.276 cmderr E [Go] [ERROR] /mnt/vss/_work/1/s/azure-sdk-for-go/src/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/fabric/armfabric/TempTypeSpecFiles/Microsoft.Fabric.Management/models.tsp:148:4 - error ambiguous-symbol: "nextLink" is an ambiguous name between TypeSpec.nextLink, Azure.Core.nextLink. Try using fully qualified name instead: TypeSpec.nextLink, Azure.Core.nextLink
07:37:50.277 cmderr E [Go] [ERROR] /mnt/vss/_work/1/s/azure-sdk-for-go/src/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/fabric/armfabric/TempTypeSpecFiles/Microsoft.Fabric.Management/models.tsp:118:4 - error ambiguous-symbol: "nextLink" is an ambiguous name between TypeSpec.nextLink, Azure.Core.nextLink. Try using fully qualified name instead: TypeSpec.nextLink, Azure.Core.nextLink
07:37:50.277 cmderr E [Go] [ERROR] Refer to the detail errors for potential fixes.
07:37:50.277 cmderr E [Go] [ERROR] If the issue persists, contact the Go language support channel at https://aka.ms/azsdk/go-lang-teams-channel and include this spec pull request.
07:37:50.277 error C Script return with result [failed] code [1] signal [null] cwd [azure-sdk-for-go/src/github.com/Azure/azure-sdk-for-go]: generator automation-v2
@wanlwanl@jianingwang123 I think this issue is resolved once the emitter is adopted to the latest(December) compiler version(Azure/azure-rest-api-specs@7e22a66). IIRC, all emitters have upgraded to that compiler version, so all should be fixed.
Description:
error ambiguous-symbol: "nextLink" is an ambiguous name between TypeSpec.nextLink, Azure.Core.nextLink. Try using fully qualified name instead: TypeSpec.nextLink, Azure.Core.nextLink
Additional context:
PR1:
Go:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4403502&view=logs&j=0303ead4-2e3b-557b-303e-fe8735d4d18f&t=b29b24f0-8be9-5e66-edce-54fd3565c09c&l=303
Java:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4403502&view=logs&j=a8a7a537-82b0-583c-7971-bac70b9822ca&t=37e3947b-3cfb-5d36-86ba-0e22bb7dbc33&l=224
Js:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4403502&view=logs&j=47092895-c7c8-567a-c7a6-8c88f3ec178e&t=d293a8e8-c6af-5091-cdf7-4c66482dd6f2&l=240
Net:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4403502&view=logs&j=03afb3bb-7296-55ad-aa07-ceee610c73b2&t=0f320c29-1c90-5304-d2d3-c58a6bb76437&l=237
Python:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4403502&view=logs&j=b7f68bce-9df8-5468-1c9f-74766cfc9a39&t=25fc8ae6-51ed-58e2-b772-f4d054412fe3&l=851
PR2:
Java:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4405085&view=logs&j=a8a7a537-82b0-583c-7971-bac70b9822ca&t=37e3947b-3cfb-5d36-86ba-0e22bb7dbc33&l=195
Js:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4405085&view=logs&j=47092895-c7c8-567a-c7a6-8c88f3ec178e&t=d293a8e8-c6af-5091-cdf7-4c66482dd6f2&l=211
.Net:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4405085&view=logs&j=03afb3bb-7296-55ad-aa07-ceee610c73b2&t=0f320c29-1c90-5304-d2d3-c58a6bb76437&l=182
Python:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4405085&view=logs&j=b7f68bce-9df8-5468-1c9f-74766cfc9a39&t=25fc8ae6-51ed-58e2-b772-f4d054412fe3&l=822
The text was updated successfully, but these errors were encountered: