Comments (3)
We are running into this error as well. We are using the legacy C# generator, so the v3: true
flag does not work in our case. Any suggestions for a different workaround?
Here is another repro:
input-file: https://github.com/Azure/azure-rest-api-specs/blob/d374d03801e97737ddb32e01f20513e7b2bbd9c3/arm-storage/2015-06-15/swagger/storage.json
csharp: true
legacy: true
from autorest.
A minimal readme.md to repro the EINVAL is:
use-extension:
"@microsoft.azure/classic-openapi-validator": "~1.1.5"
input-file: sample.yaml
ResourceHealth's config is getting this through:
azure-validator: true
This imports classic-openapi-validator if we don't also set v3: true
A workaround is to add v3: true
to the affected autorest config.
from autorest.
Well, if legacy one is still needed, and if your problem persists in your build pipelines, the only workaround could be changing your build agent to a linux one (i.e. ubuntu-latest) from windows (windows-latest).
That worked for my case.
from autorest.
Related Issues (20)
- Pass compilation for all the test projects
- Compilation fail with error " didn't specify which versions with @useDependency."
- @versioned is used without module import
- ApiVersion as path parameter not supported in openapi-to-typespec
- @encodedName don't support "json" as mime type
- Express resource hierarchy
- error | Modelerfour/IncompatibleRequestBodies | Operation 'Imports/PostImportInGroup' content types [json, multipart] have the same body schema but cannot be used together
- AnyObject as body is not correctly generated to typespec
- parent resource should be a model in the generated tsp
- autorest warning on .Net 8 app during the build process
- Improve error message if "parameters" contains "$ref"
- Add converter version info to the result
- Collison detected inserting into Object: transfer
- Improve error message "no input files provided"
- One page of issues in openapi-to-typespec
- Type http not allowed during schema validation but specified in OpenAPI specification
- Server-side Generator
- EXEC : error | error : Could not read readme.md in private repo
- reuse client when using tokens (issue #3192)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from autorest.