GTG

filtering on non-existant tags returns all tasks

Bug #602108 reported by Bryce Harrington
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GTG
Fix Released
Medium
Bryce Harrington

Bug Description

Steps to reproduce:

0. Startup gtg
1. ./gtcli postpone @NonexistantTag 2011-07-05

This should be a no-op. The tag doesn't exist, so when gtcli calls timi.get_tasks_filtered(filters) via DBUS, no tasks should be returned. Instead, it ignores the filter and returns all tasks as if that tag had not been specified as a filter.

Tags: dailyuse

Related branches

Revision history for this message
Bryce Harrington (bryce) wrote :

I've attached a branch with a change to the filter code that seems to fix it (at least for the test case in the description).

It seems that in __is_displayed(), if there is a tag filter using a tag that is not defined, it skips processing of it (which is correct) but the logic falls through to returning a True result by default. This branch changes this particular error case to default as False.

Changed in gtg:
importance: Undecided → Medium
assignee: nobody → Bryce Harrington (bryceharrington)
status: New → In Progress
milestone: none → 0.3
tags: added: dailyuse
Bryce Harrington (bryce)
Changed in gtg:
assignee: Bryce Harrington (bryce) → nobody
Revision history for this message
Lionel Dricot (ploum-deactivatedaccount) wrote :

Thanks Bryce,

We will try to merge you branch ASAP

Changed in gtg:
status: In Progress → Confirmed
status: Confirmed → In Progress
assignee: nobody → Bryce Harrington (bryce)
Changed in gtg:
milestone: 0.3 → 0.2.9
Revision history for this message
Izidor Matušov (izidor) wrote :

Thank you Bryce for the fix. LibLarch evolved over the time, I added a small fix for DBUS interface to use own LibLarch view => I had to merge it manually. I am not sure if Launchpad understands that :-)

The fix is in rev. 959.

Changed in gtg:
status: In Progress → Fix Committed
Izidor Matušov (izidor)
Changed in gtg:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.