GitLab

Gracefully handle (and notify the user) about the absence of a report_url setting at report upload-time

At some point in Python's history, the 'message' attribute on the IOError exception type was dropped.

We had been using IOError as a stand-in for the more accurate FileNotFoundError, and we don't really need to retrieve or print the original exception output, as far as I can tell.

This change updates the exception type, and emits a notification message, while retaining the existing behaviour that skips the error and continues on with starting gtimelog with an empty initial task list.

Use-case: I know I worked 20 days last month. I forgot to record a few
hours on Friday. If I fix this on Sunday, then I can just edit the
timelog and see the monthly stat and verify that the 20 days total
matches the expected value. Then submit it to chronophage.

However, I can't do the same on Monday, because we're already in March.
Fix this problem by providing stats for both the current month and the
last month.

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Python 3.8 is gone from Debian.
Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Refactored time window creation logic into TimeWindow methods (window_for_day,
window_for_week, window_for_month).

(This is a partial application of the upstream commit 08c9a1c.)

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

It's EOL upstream, and I'm tempted by f-strings and order-preserving
dictionaries.

On Ubuntu 20.04 LTS I was seeing

    /home/mg/src/gtimelog/src/gtimelog/main.py:72: PyGIWarning: Gdk was imported without specifying a version first. Use gi.require_version('Gdk', '3.0') before import to ensure that the right version gets loaded.
      from gi.repository import Gdk, Gio, GLib, GObject, Gtk, Pango, Soup

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Earlier commit started matching any of the task data, although it did
not show the full task tree, when a match was made. Namely for a given:

customer:project:group:task

If we matched the group, none of the tasks were listed. This commit
fixes that adding a blucky comment explaining the current, IMHO weird,
state of affairs.

Fixes: 11bdaaec ("gtimelog: go through all task data via the search box")
Reported-by: Fadi Abou Younes <fadi.abouyounes@collabora.com>
Signed-off-by: Emil Velikov <emil.velikov@collabora.com>

They’re ancient, broken and the upstream doesn’t like them either.
Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

This makes it easier to sync with the upstream who have reimplemented
this part of the code differently.
Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>