Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

Still StackOverflowError on some recursive schemas #9222

Open
arusakov-rh opened this issue Dec 1, 2020 · 3 comments
Open

Still StackOverflowError on some recursive schemas #9222

arusakov-rh opened this issue Dec 1, 2020 · 3 comments
Labels
cat/bug A bug which needs fixing group/server REST backend for managing integrations status/never-stale Marker that this issue should not be marked as stale

Comments

@arusakov-rh
Copy link

arusakov-rh commented Dec 1, 2020 •
edited
Loading

This is a...


[ ] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Documentation issue or request

Description

The validator made in #4714 to catch situations like #4437 doesn't seem to cover arrayssome cases, leading to the same StackOverflowError thrown when trying to load, e.g., this TM Forum API (look for ServiceOrderItem definition and serviceOrderItem array inside of it).
@arusakov-rh arusakov-rh changed the title StackOverflowError on recursive schemas involving arrays Still StackOverflowError on some recursive schemas Dec 1, 2020
@zregvart zregvart added cat/bug A bug which needs fixing group/server REST backend for managing integrations labels Dec 1, 2020
@zregvart zregvart self-assigned this Dec 1, 2020
@zregvart
Copy link
Member

zregvart commented Dec 1, 2020

We should also see if recursive references are supported in AtlasMap now, so we can support recursion and won't need the validation.

@stale
Copy link

stale bot commented Jun 11, 2021

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

@stale stale bot added the status/stale Issue considered to be stale so that it can be closed soon label Jun 11, 2021
@zregvart zregvart added the status/never-stale Marker that this issue should not be marked as stale label Jun 11, 2021
@stale stale bot closed this as completed Jun 18, 2021
@arusakov-rh
Copy link
Author

Seems that the bot ignored the never-stale flag?

@zregvart zregvart removed the status/stale Issue considered to be stale so that it can be closed soon label Jun 22, 2021
@zregvart zregvart reopened this Jun 22, 2021
@zregvart zregvart removed their assignment Sep 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
cat/bug A bug which needs fixing group/server REST backend for managing integrations status/never-stale Marker that this issue should not be marked as stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zregvart @arusakov-rh