Menu
▾
▴
#1228 2 tickets being parent for each other create loop and fatal error
It's possible to create kind of loop in ticket that generates error.
I can attach ticket B as parent ticket for ticket A, and the reverse( attach ticket A as parent ticket for ticket B).
Then on 2.2.0:
- I can update public log on ticket A and B: child(s) ticket(s) is updated
- I can 't resolve any of both ticket : I got error msg "Fatal error: Maximum function nesting level of '100' reached, aborting!"
on 2.2.1:
- I can't update public log nor can't resolve any of both ticket
maybe should we block loop creation, preventing both tickets to be parent for each other ?
Fixed by [r4045] in release 2.3.0-beta
Related
Commit: <Commit _id='5358055aa02bb175d1406271:4045' tree_id='7f54df4b0d757e9466c57be75a41d9dced4bcf1b' committed=I{'date': datetime.datetime(2016, 5, 10, 15, 33, 48, 80000), 'email': '', 'name': 'dflaven'} authored=I{'date': datetime.datetime(2016, 5, 10, 15, 33, 48, 80000), 'email': '', 'name': 'dflaven'} message='Prevent infinite cross-ticket recursion when propagating parent->child resolution in tickets.' parent_ids=I['5358055aa02bb175d1406271:4044'] child_ids=I['5358055aa02bb175d1406271:4046'] repo_ids=I[ObjectId('5358055aa02bb175d1406271')]>