gtimelog merge requestshttps://gitlab.collabora.com/collabora/gtimelog/-/merge_requests2023-11-09T08:04:14Zhttps://gitlab.collabora.com/collabora/gtimelog/-/merge_requests/35Use (gi.)require_version() as applicable2023-11-09T08:04:14ZEmil VelikovUse (gi.)require_version() as applicableHandful of places were lacking the version check resulting in warning or
errors. For example: on my system soup 3.0 got picked which has
different API.
Signed-off-by: Emil Velikov <emil.velikov@collabora.com>
/cc @andrewsh fyiHandful of places were lacking the version check resulting in warning or
errors. For example: on my system soup 3.0 got picked which has
different API.
Signed-off-by: Emil Velikov <emil.velikov@collabora.com>
/cc @andrewsh fyihttps://gitlab.collabora.com/collabora/gtimelog/-/merge_requests/33Fix warnings from flake8.2023-04-05T14:46:02ZJeremy WhitingFix warnings from flake8.Added spaces after assert before (Added spaces after assert before (Jeremy WhitingJeremy Whitinghttps://gitlab.collabora.com/collabora/gtimelog/-/merge_requests/31Fix hiding "Success" and "Error" dialogs on kwin/plasma.2023-04-05T14:40:20ZJeremy WhitingFix hiding "Success" and "Error" dialogs on kwin/plasma.When submitting timesheets for the last decade or so every time
the success window shows up behind the main gtimelog window.
Setting the parent of the Gtk.MessageDialog to the mainwindow instead
of the submit_window which has hidden by t...When submitting timesheets for the last decade or so every time
the success window shows up behind the main gtimelog window.
Setting the parent of the Gtk.MessageDialog to the mainwindow instead
of the submit_window which has hidden by this point fixes this
annoyance...Jeremy WhitingJeremy Whitinghttps://gitlab.collabora.com/collabora/gtimelog/-/merge_requests/32Tell pip to break system packages (we don’t care)2023-04-05T13:53:13ZAndrej Shaduraandrew.shadura@collabora.co.ukTell pip to break system packages (we don’t care)Since recently, Python started detecting externally managed
environments such as apt-installed package in Debian. Since
we run tests in an isolated environment, we don’t care if we
break something by install Python dependencies.
```
err...Since recently, Python started detecting externally managed
environments such as apt-installed package in Debian. Since
we run tests in an isolated environment, we don’t care if we
break something by install Python dependencies.
```
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.
If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.
If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.
See /usr/share/doc/python3.11/README.venv for more information.
```https://gitlab.collabora.com/collabora/gtimelog/-/merge_requests/30allowing to define a custom Authorization header for back-end calls2023-02-21T12:42:22ZVinícius Fernandes Moreiraallowing to define a custom Authorization header for back-end callsAllowing to define a custom Authorization header for the back-end calls in case is required (We will need for future releases of Chronophage)Allowing to define a custom Authorization header for the back-end calls in case is required (We will need for future releases of Chronophage)Vinícius Fernandes MoreiraVinícius Fernandes Moreirahttps://gitlab.collabora.com/collabora/gtimelog/-/merge_requests/29Use GLib to send notifications2021-07-22T10:03:59ZCorentin NoëlUse GLib to send notificationsAvoid using libnotify when all we need is already in GLib.Avoid using libnotify when all we need is already in GLib.https://gitlab.collabora.com/collabora/gtimelog/-/merge_requests/28[20210405] flake8 cleanup2021-04-12T12:29:52ZJames Addison[20210405] flake8 cleanupCleans up a few `flake8` lint-related warnings in the codebase.Cleans up a few `flake8` lint-related warnings in the codebase.https://gitlab.collabora.com/collabora/gtimelog/-/merge_requests/27Improve handling of missing report_url setting at report upload-time2021-04-12T12:25:58ZJames AddisonImprove handling of missing report_url setting at report upload-timeGracefully handle (and notify the user) about the absence of a `report_url` setting at report upload-time.Gracefully handle (and notify the user) about the absence of a `report_url` setting at report upload-time.https://gitlab.collabora.com/collabora/gtimelog/-/merge_requests/26Improve handling for missing tasks.txt at startup2021-04-12T12:21:41ZJames AddisonImprove handling for missing tasks.txt at startupAt 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 ori...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.
Closes #4.https://gitlab.collabora.com/collabora/gtimelog/-/merge_requests/25main window: add summary for the last month as well2021-03-25T10:17:26ZMiklos Vajnamain window: add summary for the last month as wellUse-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...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.https://gitlab.collabora.com/collabora/gtimelog/-/merge_requests/24Display an error bar if bad entries are found in the timelog2021-02-23T20:15:19ZAndrej Shaduraandrew.shadura@collabora.co.ukDisplay an error bar if bad entries are found in the timelogJust printing the error is not enough since it goes to the X log or the journal and is effectively lost.
Let the user know there’s something wrong.Just printing the error is not enough since it goes to the X log or the journal and is effectively lost.
Let the user know there’s something wrong.https://gitlab.collabora.com/collabora/gtimelog/-/merge_requests/23gtimelog: display the full tree on match2020-10-08T12:19:36ZEmil Velikovgtimelog: display the full tree on matchEarlier 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 comm...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: 11bdaae ("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>https://gitlab.collabora.com/collabora/gtimelog/-/merge_requests/12gtimelog: go through all task data via the search box2020-10-07T12:32:48ZEmil Velikovgtimelog: go through all task data via the search boxUnlike upstream, we have a segmented task list. In consists of four
components - customer:project:group:task
Currently when the user writes "test", while searching for tasks, the
text is matched only with the "group" entries. This is fa...Unlike upstream, we have a segmented task list. In consists of four
components - customer:project:group:task
Currently when the user writes "test", while searching for tasks, the
text is matched only with the "group" entries. This is fairly misleading
since the user may be looking for the any of the four.
Reported-by: Eze Garcia <ezequiel@collabora.com>
Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
/cc @ezequielhttps://gitlab.collabora.com/collabora/gtimelog/-/merge_requests/22Drop ancient scripts2020-10-05T18:25:41ZAndrej Shaduraandrew.shadura@collabora.co.ukDrop ancient scriptsThey’re ancient, broken and the upstream doesn’t like them either.
@evelikov, @rpavlik, what do you think, does anyone at Collabora use these?They’re ancient, broken and the upstream doesn’t like them either.
@evelikov, @rpavlik, what do you think, does anyone at Collabora use these?https://gitlab.collabora.com/collabora/gtimelog/-/merge_requests/21Split keyring and secret handling off into a separate module2020-10-05T15:08:19ZAndrej Shaduraandrew.shadura@collabora.co.ukSplit keyring and secret handling off into a separate moduleThis makes it easier to sync with the upstream who have reimplemented
this part of the code differently.This makes it easier to sync with the upstream who have reimplemented
this part of the code differently.https://gitlab.collabora.com/collabora/gtimelog/-/merge_requests/20Tiny fixes2020-10-01T07:03:32ZAndrej Shaduraandrew.shadura@collabora.co.ukTiny fixeshttps://gitlab.collabora.com/collabora/gtimelog/-/merge_requests/19Use flake8 instead of running pycodestyle directly2020-10-01T06:51:18ZAndrej Shaduraandrew.shadura@collabora.co.ukUse flake8 instead of running pycodestyle directlyUse flake8 instead of running pycodestyle directly gives a bit saner output.Use flake8 instead of running pycodestyle directly gives a bit saner output.https://gitlab.collabora.com/collabora/gtimelog/-/merge_requests/18Fix rlTimeLog2020-10-01T06:33:24ZAndrej Shaduraandrew.shadura@collabora.co.ukFix rlTimeLoghttps://gitlab.collabora.com/collabora/gtimelog/-/merge_requests/17Update setuptools stuff2020-09-30T19:27:14ZAndrej Shaduraandrew.shadura@collabora.co.ukUpdate setuptools stuff* Update the manifest
* Update setup.py
* Depend on PyGObject explicitly in setup.py* Update the manifest
* Update setup.py
* Depend on PyGObject explicitly in setup.pyhttps://gitlab.collabora.com/collabora/gtimelog/-/merge_requests/16Debian packaging and CI cleanup2020-09-30T18:55:12ZAndrej Shaduraandrew.shadura@collabora.co.ukDebian packaging and CI cleanup* Update packaging
* Adjust the CI to use build-depends* Update packaging
* Adjust the CI to use build-depends