Intermittent segfault when calling `Expression.find_all` about sqlglot HOT 4 CLOSED

Yeah makes sense, thanks for the report. Unfortunately I don't think we've seen something similar in the past.

from sqlglot.

Not sure there's an action item here for us, I can't see how this could be related to find_all's implementation. May be a Python / lib (eg. deque?) issue. I tried this a few times but none of them crashed.

Feel free to let us know if you find something interesting or figure out a way to reproduce this consistently, and we can take a closer look.

from sqlglot.

It also looks like your sqlglot version is older, not sure if that's the root cause here but maybe try updating? There have been some major updates in find_all since v17, if I remember correctly.

from sqlglot.

Not sure there's an action item here for us, I can't see how this could be related to find_all's implementation. May be a Python / lib (eg. deque?) issue. I tried this a few times but none of them crashed.

I figured I'd report it anyway just in case you knew what happened.

It also looks like your sqlglot version is older, not sure if that's the root cause here but maybe try updating? There have been some major updates in find_all since v17, if I remember correctly.

I'll see if we can, this is a work project so the update would have to be coordinated.

from sqlglot.