Skip to content
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

Maximum Recursion Depth Exceeded #20

Closed
larsenweigle opened this issue May 7, 2024 · 1 comment
Closed

Maximum Recursion Depth Exceeded #20

larsenweigle opened this issue May 7, 2024 · 1 comment

Comments

@larsenweigle
Copy link

larsenweigle commented May 7, 2024

Description

When executing certain queries involving nested answer calls within the WHERE clause, the system exceeds the maximum recursion depth.

Query Example

SELECT courses.title, courses.course_codes, offerings.days, offerings.start_time, offerings.end_time, offerings.season
FROM courses
JOIN offerings ON courses.course_id = offerings.course_id
WHERE offerings.season = 'spring'
AND (
    answer(description, 'does this course provide a solid mathematical foundation for research in Natural Language Processing?') = 'Yes'
    OR answer(description, 'does this course focus on Language Modelling?') = 'Yes'
);

Error Message

The system throws a "maximum recursion depth exceeded" error as detailed below:

maximum recursion depth exceeded
Traceback (most recent call last):
  File "/home/larsen/course-companion/sql_free_text_support/execute_free_text_sql.py", line 1086, in suql_execute_single
    visitor(root)
  ...
  File "/usr/lib/python3.8/copy.py", line 270, in _reconstruct
    state = deepcopy(state, memo)
  ...
  File "/usr/lib/python3.8/copy.py", line 230, in _deepcopy_dict
    y[deepcopy(key, memo)] = deepcopy(value, memo)
  ...
RecursionError: maximum recursion depth exceeded while calling a Python object
george1459 added a commit that referenced this issue May 7, 2024
@george1459 george1459 mentioned this issue May 7, 2024
george1459 added a commit that referenced this issue May 7, 2024
@george1459
Copy link
Contributor

@larsenweigle Thanks! 1.1.7a2 (or the latest master branch) should have fixed it. Please test and see if the issue persists.

@george1459 george1459 mentioned this issue May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants