-
Notifications
You must be signed in to change notification settings - Fork 737
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
Error: There are multiple operations defined for 'get: <path>' #4898
Comments
This one looks expected to me |
from the place where this error is emitted
autorest is basically just a pipeline runner. It provides all those plugins where a few are those old legacy one(including this new composer. I have no idea why you still be calling this here. The duplicate operation is also something I am just confused it would ever work. The only things that I can see autorest was kinda design to work with is if you loaded different version of the same api but that's something we never actually did. The previous bug I fixed was bad in the sense that it was just crashing with a meaningless message and that's not something we should do. |
So digging into that, it might be getting there because of autorest deciding to run the legacy pipeline by default. Maybe we could not do that anymore(though I am worried this will break existing flow) so maybe have a flag. However my last point still stand. Even though the linter flow might not complain about that it would still fail later. |
I think this was a temporary bug in the spec -- it's since been updated to remove the dup operations. Closing for now, will re-open if this becomes a recurring problem. |
Repro Steps
Checkout Azure/azure-rest-api-specs@0817dfd
Bugs
This one repro has exposed multiple bugs.
The first exception was:
This was fixed in #4896.
However, running the repro after this fix leads to another exception:
The text was updated successfully, but these errors were encountered: