-
Couldn't load subscription status.
- Fork 709
[bug][jira] jira get_issue_tree_recursive method overwrites default params values from previous executions #1461
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
Conversation
…ments_ids_from_issue
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1461 +/- ##
==========================================
- Coverage 34.42% 34.41% -0.02%
==========================================
Files 46 46
Lines 8627 8631 +4
Branches 1611 1610 -1
==========================================
Hits 2970 2970
- Misses 5530 5536 +6
+ Partials 127 125 -2 ☔ View full report in Codecov by Sentry. |
Steps to reproduce
Let's say we have two jira issues:
First iteration will return 2 but the second iteration of the loop with return 6 (including the result from previous execution of the loop).
Rootcause
It is caused by python "gotcha": mutable default arguments - https://docs.python-guide.org/writing/gotchas/#mutable-default-arguments
In the code we have initiation of the tree parameter:
def get_issue_tree_recursive(self, issue_key, tree=[], depth=0)Each execution of the query will overwrite the tree param. The way to fix it is to:
def get_issue_tree_recursive(self, issue_key, tree=None, depth=None): <...> if tree is None: tree = [] if depth is None: depth = 0 (...)PR solves this specific bug in the get_issue_tree_recursive method.