FilteredTree: error displayed when trying to make a task a child of its own chilld
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GTG |
Fix Released
|
Critical
|
Unassigned |
Bug Description
Steps to reproduce:
0. ./scripts/debug.sh
1. Drag 'Reporting bugs' onto 'Learn how to use the Workview'
2. There are now two 'Reporting bugs' tasks, the first as a child of 'Learn how to use the Workview', the second under 'Getting started with GTG'
3. Drag 'Learn how to use the Workview (1)' to the first 'Reporting bugs' task (so it will become a grandparent of itself)
4. The following errors messages appear:
*** Node 3@1 not in vr and no path for parent
*** please report a bug against FilteredTree
Error :! no path for node 3@1 !
*** Node 3@1 not in vr and no path for parent
*** please report a bug against FilteredTree
*** Node 5@1 not in vr and no path for parent
*** please report a bug against FilteredTree
Error :! no path for node 5@1 !
*** Node 3@1 not in vr and no path for parent
*** please report a bug against FilteredTree
Error :! no path for node 3@1 !
*** Node 3@1 not in vr and no path for parent
*** please report a bug against FilteredTree
*** Node 5@1 not in vr and no path for parent
*** please report a bug against FilteredTree
Error :! no path for node 5@1 !
*** Node 3@1 not in vr and no path for parent
*** please report a bug against FilteredTree
*** Node 5@1 not in vr and no path for parent
*** please report a bug against FilteredTree
Error :! no path for node 5@1 !
*** Node 3@1 not in vr and no path for parent
*** please report a bug against FilteredTree
Error :! no path for node 3@1 !
tags: | added: regression |
Changed in gtg: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
milestone: | none → 0.3 |
Changed in gtg: | |
status: | Confirmed → In Progress |
Changed in gtg: | |
milestone: | 0.3 → 0.2.9 |
Changed in gtg: | |
status: | Fix Committed → Fix Released |
The point 2. is, in fact, bug #540616