Invalid Swagger Format

[naveenn2n]

Hi Team,

We are getting invalid swagger format while loading the json file.
�[91merror:�[0m Invalid swagger format.

As per our observation, we are using petsore swagger version.

[domanchi]

Hi @naveenn2n,

Please provide more information so that we can reproduce the issue. It does not throw this error for me on master.

[naveenn2n]

Hi @domanchi ,

{"swagger":"2.0","info":{"version":"v1", this is the swagger information we provided. Due to privacy issues. I am unable to show content of json.

Please find below screenshots for more information.
Error Screenshot
https://user-images.githubusercontent.com/6263232/80711278-bc682900-8b0d-11ea-98a9-760b4364a11a.png

and Json format Screenshot
https://user-images.githubusercontent.com/6263232/80711456-018c5b00-8b0e-11ea-8fe3-e32f5c170838.PNG

[toptotu]

Hi @naveenn2n,

Please provide more information so that we can reproduce the issue. It does not throw this error for me on master.

I also encountered the same problem. The YAML file path is https://www.3gpp.org/ftp/Specs/archive/29_series/29.510/OpenAPI/2018-12/TS29510_Nnrf_NFManagement.yaml

[AlexB1986]

Hi @naveenn2n,
Please provide more information so that we can reproduce the issue. It does not throw this error for me on master.

I also encountered the same problem. The YAML file path is https://www.3gpp.org/ftp/Specs/archive/29_series/29.510/OpenAPI/2018-12/TS29510_Nnrf_NFManagement.yaml

Hi @toptotu, your specification is in OpenAPI v3 format, but fuzz-lightyear use Bravado library that does not support OpenAPI v 3 -- please see Yelp/bravado#306

[AlexB1986]

Hi @naveenn2n , do you use integer keys (like 200) or string (like '200') in response codes?
We faced that under Windows env with integer keys in response codes fuzz-lightyear produces "Invalid Swagger Format".
You may try:

• use Linux env;
• OR to fix specification -- integer keys in response codes--> string (200 --> '200')

Hope, it will help.