gtg
gtg copied to clipboard
getting-things-gnome
Creating repeating weekly/monthly/yearly tasks with the Quick Add syntax causes a traceback on startup ('Date' object has no attribute 'strftime')
Context: Global generic exception
Traceback (most recent call last):
File "/app/lib/python3.9/site-packages/GTG/gtk/browser/main_window.py", line 1060, in on_edit_active_task
self.app.open_task(tid)
File "/app/lib/python3.9/site-packages/GTG/gtk/application.py", line 553, in open_task
editor = TaskEditor(requester=self.req, app=self, task=task,
File "/app/lib/python3.9/site-packages/GTG/gtk/editor/editor.py", line 98, in __init__
self.recurring_menu = RecurringMenu(self.req, task.tid, self.builder)
File "/app/lib/python3.9/site-packages/GTG/gtk/editor/recurring_menu.py", line 45, in __init__
self.update_header()
File "/app/lib/python3.9/site-packages/GTG/gtk/editor/recurring_menu.py", line 125, in update_header
month=date.strftime('%B'), day=date.strftime('%d')))
AttributeError: 'Date' object has no attribute 'strftime'
Software versions:
- Getting Things GNOME! v0.6
- CPython 3.9.9 (main, Nov 10 2011, 15:00:00) [GCC 11.3.0]
- GTK 3.24.34, GLib 2.70.5
- PyGLib 3.42.2, PyGObject 3.42.2
- Linux-6.0.6-76060006-generic-x86_64-with-glibc2.33
Dunno, I'm new to this software, seems like it occurs when set ever:year and no starting date
Cannot open the tasks to edit them Setting a starting date doesn't fix it
100% of my tasks are bugged, only the default tasks are working -__-
Ok so when I follow the F1 help, I type one of the example: pay my taxes every:year in the quick entry
It works. I close the program, reopen it and then the error above
Nobody uses repetitive tasks? it's unusable :(
Same here. For now it works only if you turn off repetition before editing a task and then you can turn it on. Not a smooth workaround but at least this way it works.
Nobody uses repetitive tasks? it's unusable :(
Same here. For now it works only if you turn off repetition before editing a task and then you can turn it on. Not a smooth workaround but at least this way it works.
thank you!! gonna try tomorrow to see if recurring task works even when buggy
because of this bug I even looked for another software to replace gtg but i don't know...
@consmm I don't know why but I made a recurring task "test" and can edit it. Then I added tags and subtask, but I still can edit it...
Why this one is not buggy??
Nobody uses repetitive tasks? it's unusable :(
Personally I (and many others) have been using recurring tasks intensively for the past two years without issues.
I've been using the feature only with the right-click and toolbar button GUI methods. I've never tested the quick-add syntax for it, so that part might be broken, I don't know.
Try with other parts of the GUI first, to determine if your problem is specific to the quick-add entry field method; if so, then you can refocus your bug report with clearer reproduction steps; ideally you could take a look at the code to see why its logic is not parsing your syntax correctly, though realistically this is not going to be fixed before #627 and #894.
I tried with quick add a simple "test every:day" and it works,
So I identified the issue: if you use recurring task (with quick add or right click) with "every day" or "very other day" it works fine If you set it to recurring week/month/year, and then you close GTG and reopen it, then it suddenly is uneditable
@nekohayo
damn annoying when you report an issue and owner/members tell you to fix it yourself though, especially when you just discovered the app and cannot really use it cause of the bug
PS: https://github.com/getting-things-gnome/gtg/pull/943
@BarbzYHOOL @nekohayo yes, if PR #943 is accepted, it will resolve this issue. Although it's arising in a different line of code, the cause of this bug is the exact same as #870.
Realistically, given how thin we are stretched and how it will almost certainly conflict with those code changes, I still believe this can only be addressed once the 200+ commits from PR #894 land (yes, we're working on it); once that done, then it can be retested and (if the issue still occurs there) #943 would need to be rebased and adapted to the new codebase...
damn annoying when you report an issue and owner/members tell you to fix it yourself though, especially when you just discovered the app and cannot really use it cause of the bug
Welcome to community-driven unpaid open source development.
Also, what I said was, "ideally you could take a look at the code to see why its logic is not parsing your syntax correctly", that's not the same as "fix it yourself or gtfo". It's a perfectly polite and reasonable ask to get help investigating the issue when everybody else is already swamped. Especially with the words "ideally" and "could".
anyone knows a good alternative to gtg???
It is rude (and pointless*) to ask this question to developers of said application, who are doing work for free in their spare time. Solutions and new releases don't happen overnight. Please keep your expectations in check.
*: "pointless" because the reason why I (and various others) help the GTG project is because I believe there is no 1:1 alternative. It is impossible for me to make a recommendation, because I wouldn't use anything else.
Retitled & retagged for clarity.
I've set priority to "medium" instead of high, because at least there is a workaround from a user's stand point: instead of the quick add syntax for recurring tasks, you can simply use the recurrence GUI within the task editor window or with the right-click menus on an existing task. It works fine (at least for me and the others who have used the app this way so far)... That's easier than trying to find a replacement app ;)
I was not asking devs but users
you've probably seen it a hundred times, on abandoned projects, you can exchange with users who are sad that it's no longer maintained. Since nobody answered at all for several months and since the issue exists for 1 year, I could clearly conclude that it was not gonna be fixed.
Your workaround doesn't work at all, I tried both of them and it is still the same issue after I reopen GTG (I repeat, you have to close GTG and reopen it...). You should remove the feature altogether instead. During 1 year, people joined and expected this basic feature to work but that's not the case. To be fair I've watched your videos (if i recall right, one was like "this is the best tool i've used for 10 years and it's free!"), learned the tutorial and still not using GTG at all because of this issue, so it didn't make me gain any time but rather lose time. It's free but i've been mislead, time is not free.
Finally about "welcome to open source", I was the leader of a big open source project (actually 3k stars) and I always tried to find solutions to major issues like this and especially not deter new users by asking them to fix it themselves (no matter how polite it is said), not even knowing if they knew how to code one bit...
Anyway, not trying to make you mad, but if I insist, it's because it's a big issue to waste time with weird workarounds (see one of the comment above) for such a tool that is designed to make you gain time. Also because your video and the tutorial may have convinced me that it's a good system
The same issue have been reported in the Debian bug tracking system: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033156
I can see a patch in https://github.com/getting-things-gnome/gtg/pull/943. Is it safe to use it as long as there is no official fix?
Thanks,
I believe it should, yes.
On Mon, Feb 26, 2024 at 9:17 PM Jeff @.***> wrote:
Hi @APCBoston https://github.com/APCBoston, is your PR #943 https://github.com/getting-things-gnome/gtg/pull/943 supposed to (maybe incidentally) fix this?
— Reply to this email directly, view it on GitHub https://github.com/getting-things-gnome/gtg/issues/950#issuecomment-1965667396, or unsubscribe https://github.com/notifications/unsubscribe-auth/AODAH7LB2B7RP7BSRGJEKRTYVU62NAVCNFSM6AAAAAATV4T3ISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRVGY3DOMZZGY . You are receiving this because you were mentioned.Message ID: @.***>
-- Andrew W. Piltser-Cowan @.***
