question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Compatibility issues with latest autorest

See original GitHub issue

Before filling a bug

  • have you checked the faq for known issues.
  • have you checked existing issues

Describe the bug Previously version of autorest 3.1 started giving problems and i was forced to upgrade. The latest autorest 3.4 is using latest extensions of core and python which inherently is forcing us change versions of other packages likes moto, boto, boto3, botocore …etc.

Please provide as much information as you can. This would be:
- OpenAPI files having the issues
- Autorest command used

Expected behavior

After generating the autorest latest client, when making the request firstly it showed an error for the from azure.core.rest import HttpRequest rest not found – I was using azure-core 1.12, updating it to 1.18 resolved the problem. Then it started giving AttributeError: ‘_patch’ object has no attribute 'is_local Then updating mock version resolved this issue. However from mock, it depends/ has compatibility issues with moto, which indeed forced me to update versions of boto, boto3, botocore.

Additional context These are the current versions i’m using. Autorest versions [cli version: 3.4.0; node: v14.18.0] autorest/core – 3.6.3 info | Installing AutoRest extension ‘@autorest/python’ (latest) info | Installed AutoRest extension ‘@autorest/python’ (latest->5.9.1) info | Installing AutoRest extension ‘@autorest/modelerfour’ (~4.19.1) info | Installed AutoRest extension ‘@autorest/modelerfour’ (~4.19.1->4.19.3)

Previously was using 3.1 – is there any way, we can still continue using 3.1 and not upgrade or forced to update ?

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:6 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
babayevanuranacommented, Oct 13, 2021

Gooodd

0reactions
msftbot[bot]commented, Nov 3, 2021

Hi, we’re sending this friendly reminder because we haven’t heard back from you in 7 days. We need more information about this issue to help address it. Please be sure to give us your input. If we don’t hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Swashbuckle and Autorest compatibility (getting Data ... - GitHub
1 Swashbuckle.AspNetCore and latest autorest. We're able to generate swagger json file but then autorest fails to generate typescript client ...
Read more >
Fix Autorest Problems Generating a C# Client with .NET 6
This post shows how to fix common problems when generating an autorest client for C# with the new CSharp code generator.
Read more >
Integrating Autorest Clients with HttpClientFactory and DI
Discussing the problems and possible solutions to use generated autorest clients together with the new HttpClientFactory from Microsoft.
Read more >
Why does Visual Studio 2017 fail to generate REST API client ...
Visual Studio 2017 is using a very old version of AutoRest. The issue you are seeing is this one which was fixed in...
Read more >
autorest - npm
Input to AutoRest is an OpenAPI spec that describes the REST API.. Latest version: 3.6.2, last published: a month ago.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found