timekpr - Keep control of computer usage

No "too late" notification from timekpr-client

Reported by Roman Bazalevsky on 2012-09-24
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
timekpr
Undecided
Olli-Pekka Wallin

Bug Description

For example, if you set user time boundaries to "from 8 to 22", you will receive "too early" notification when you login as 7, but you will not receive any message, when you logging in at, lets say, 22:30, you will be just kicked off by daemon.

In timekprcommon.py we see:

def islate(bto, allowfile):
       . . .
    if (hour > bto[index]):
        if isfile(allowfile):
       . . .

So you will get notification only 1 hour after time boundary (i.e. in 23:00, if boundary is set to 22:00).

Shoud be replaced with:

    if (hour >= bto[index]):

Related branches

Changed in timekpr:
assignee: nobody → Olli-Pekka Wallin (hozmaster)
status: New → In Progress
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers