Skip to content

Add reproducing test cases for stackoverflows #16787

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ahmed-mez
Copy link
Contributor

@ahmed-mez ahmed-mez commented Jul 15, 2025

Which issue does this PR close?

  • Closes #.

Rationale for this change

This is a reproducer for #16788. See the issue for more context.

What changes are included in this PR?

An ignored test case that reproduces stack-overflows

Are these changes tested?

N/A

Are there any user-facing changes?

No

@github-actions github-actions bot added the substrait Changes to the substrait crate label Jul 15, 2025
@ahmed-mez ahmed-mez marked this pull request as ready for review July 15, 2025 12:38
@ahmed-mez ahmed-mez changed the title Add reproducing test cases Add reproducing test cases for stackoverflows Jul 15, 2025
@alamb
Copy link
Contributor

alamb commented Jul 15, 2025

cc @gabotechs and @LiaCastaneda

Copy link
Contributor

@gabotechs gabotechs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 nice reproducer!

const DEPTH: usize = 3000;

#[tokio::test]
#[ignore]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe add a comment about why is it ignored?

Copy link
Contributor

@gabotechs gabotechs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you think there could be a way of replicating this with the SQL path? something like dynamically building a deeply nested SQL statement that produces the same outcome?

There might be some value in showing the community that this is issue is not exclusive to Substrait, it might help gain some traction.

@comphead
Copy link
Contributor

I'm just wondering should it be Gist instead? 🤔

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

Successfully merging this pull request may close these issues.

4 participants