Skip to content

Long analysis of nested propel query #8865

@alfredbez

Description

@alfredbez

Bug report

We already talked about having problems with analyzing propel queries, e.g. in #4581 and here.

The full scan of our project takes almost one hour and I realized, that most of the time is spent on a few files. One of them takes more than 10 minutes in our setup. I was able to extract the file and reproduce that in a Spryker demo shop here on GitHub. You can find the repository here, Github Actions is configured and taking a bit more than 5 minutes to analyze the single file.

Code snippet that reproduces the problem

Hard to reproduce on the playground, but you can check out the repository. Apologies for the big repository, but you can just have a look at my latest commit.

Expected output

I would expect a runtime in the area of a few seconds (or even milliseconds), but not in some minutes.

Did PHPStan help you today? Did it make you happy in any way?

I really appreciate the effort all of you put into that and how fast and professionally you move that tool forward, keep up the great work 🚀

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions