Bug 1838481 - creating a build from file results in "RecursionError: maximum recursion depth exceeded while calling a Python object"
Summary: creating a build from file results in "RecursionError: maximum recursion dept...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Copr
Classification: Community
Component: cli
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Copr Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-21 08:50 UTC by Tomas Tomecek
Modified: 2020-12-11 17:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-11 17:35:32 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github packit-service packit-service issues 415 0 None closed tuned build failing with "maximum recursion depth exceeded" 2020-12-11 17:34:11 UTC

Description Tomas Tomecek 2020-05-21 08:50:04 UTC
Description of problem:

This is the stack trace within the library:


copr/v3/requests.py in endpoint_url at line 43:

  endpoint = self.endpoint.strip("/").format(**self.params)


copr/v3/helpers.py in wrapper at line 59

  result = func(*args, **kwargs)


The `result = func(...)` is where the recursion is happening.


The thing is this problem is intermittent and not fully reproducible.




Version-Release number of selected component (if applicable):
copr	1.101

Comment 1 Pavel Raiskup 2020-05-21 09:10:24 UTC
Thanks for the report.

Comment 2 Pavel Raiskup 2020-05-21 12:04:56 UTC
https://pagure.io/copr/copr/pull-request/1381

Comment 3 Pavel Raiskup 2020-06-20 06:17:30 UTC
Fix is ready in updates-testing.

Comment 4 Pavel Raiskup 2020-09-07 07:31:55 UTC
Seems like this problem is back:
https://github.com/packit/packit-service/pull/626

Comment 5 Pavel Raiskup 2020-12-11 17:35:32 UTC
Resolved via https://pagure.io/copr/copr/issue/1499


Note You need to log in before you can comment on or make changes to this bug.