Skip to content
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

OpenAPI spec - Range Error #3663

Open
Vincentv92 opened this issue Dec 16, 2024 · 8 comments
Open

OpenAPI spec - Range Error #3663

Vincentv92 opened this issue Dec 16, 2024 · 8 comments
Assignees

Comments

@Vincentv92
Copy link

          Still seeing this issue when importing Jira's OpenAPI spec: https://dac-static.atlassian.com/cloud/jira/platform/swagger-v3.v3.json?_v=1.7513.0-0.1310.0

I'm running Bruno v1.31.0

Slightly different stack trace here though:

RangeError: Maximum call stack size exceeded
    at resolveRefs (871-7fa6c933a094f6be.js:1:24965)
    at resolveRefs (871-7fa6c933a094f6be.js:1:26496)
    at resolveRefs (871-7fa6c933a094f6be.js:1:26496)
    at resolveRefs (871-7fa6c933a094f6be.js:1:26496)
    at 871-7fa6c933a094f6be.js:1:25210
    at Array.map (<anonymous>)
    at resolveRefs (871-7fa6c933a094f6be.js:1:25187)
    at resolveRefs (871-7fa6c933a094f6be.js:1:26496)
    at resolveRefs (871-7fa6c933a094f6be.js:1:26496)
    at resolveRefs (871-7fa6c933a094f6be.js:1:26496)
BrunoError: An error occurred while parsing the OpenAPI collection
    at 871-7fa6c933a094f6be.js:1:28585
    at new Promise (<anonymous>)
    at parseOpenApiCollection (871-7fa6c933a094f6be.js:1:27548)

Originally posted by @tlund101 in #939 (comment)


For a propriety API i also run into this issue, is there something else we need to provide?

@sreelakshmi-bruno sreelakshmi-bruno self-assigned this Dec 17, 2024
@talkingjd72
Copy link

talkingjd72 commented Dec 17, 2024

I am running into this as well.

@sreelakshmi-bruno
Copy link
Collaborator

Hi, I'm able to reproduce this issue, We're investigating this. Thanks!

@gajanak
Copy link

gajanak commented Jan 22, 2025

Importing OpenAPI v3.1 from OWASP dependencytrack.org
Public Sample I found : https://yoursky.blue/_app/immutable/assets/dt-v3.BN_NvSKR.yaml

Version 1.38.1

index.1962d89a.js:4 RangeError: Maximum call stack size exceeded
    at index.1962d89a.js:4:8234
    at Array.map (<anonymous>)
    at iS (index.1962d89a.js:4:8230)
    at iS (index.1962d89a.js:4:8474)
    at iS (index.1962d89a.js:4:8474)
    at iS (index.1962d89a.js:4:8474)
    at iS (index.1962d89a.js:4:8474)
    at iS (index.1962d89a.js:4:8474)
    at iS (index.1962d89a.js:4:8474)
    at iS (index.1962d89a.js:4:8474)
(anonymous) @ index.1962d89a.js:4
iU @ index.1962d89a.js:4
Promise.then
(anonymous) @ index.1962d89a.js:4
iT @ index.1962d89a.js:4
s @ index.1962d89a.js:4
uU @ lib-react.41929aa2.js:2
(anonymous) @ lib-react.41929aa2.js:2
tC @ lib-react.41929aa2.js:2
uW @ lib-react.41929aa2.js:2
sK @ lib-react.41929aa2.js:2
sQ @ lib-react.41929aa2.js:2
index.1962d89a.js:4 BrunoError: An error occurred while parsing the OpenAPI collection
    at index.1962d89a.js:4:10282
    at new Promise (<anonymous>)
    at iU (index.1962d89a.js:4:9308)
(anonymous) @ index.1962d89a.js:4
Promise.catch
(anonymous) @ index.1962d89a.js:4
iT @ index.1962d89a.js:4
s @ index.1962d89a.js:4
uU @ lib-react.41929aa2.js:2
(anonymous) @ lib-react.41929aa2.js:2
tC @ lib-react.41929aa2.js:2
uW @ lib-react.41929aa2.js:2
sK @ lib-react.41929aa2.js:2
sQ @ lib-react.41929aa2.js:2

@sreelakshmi-bruno
Copy link
Collaborator

Hi, sharing quick update: this is expected to go out in the upcoming release (likely early next week).

@AndreasEK
Copy link

Nice, anything we can do in the meantime to get the file passed? I'm assuming it's a circular dependency somewhere, is it?

@sreelakshmi-bruno
Copy link
Collaborator

Hi, we'll share a beta build within next two days with the fix so that you can use it until we have an official release.

@sreelakshmi-bruno
Copy link
Collaborator

Hi, apologies for the delay, we have a nightly build for this issue, please test it and let me know how it goes. Thanks!

@Vincentv92
Copy link
Author

For me this specific issue has been resolved, also for the propriety private API its working 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants