Skip to content

Avoid the "maximum recursion depth exceeded" RuntimeError with nested specifications #2

Description

@fogathmann

We currently traverse specification trees during evaluation recursively, which, for very deeply nested criteria, leads to the infamous RuntimeError: maximum recursion depth exceeded exception. This needs to be fixed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions