Closed k4y4k closed 2 years ago
If I'm remembering correctly I think this may be caused by a regression in taskwarrior 2.5.2. You might try downgrading taskwarrior to 2.5.1.
Epic. Now it's working. Cheers!
I have the same issue with jira service, taskwarrior version is 2.5.3 How about reopening the issue?
BUT, @bjakubiak, is there any reason you can't just grab / compile taskwarrior 2.5.1? Compiling is pretty simple / doesn't take too long, if you're a bit sketch on the idea
For the record, I don't think there's anything to be done in bugwarrior for this. I believe the upstream bug is https://github.com/GothenburgBitFactory/taskwarrior/issues/1953 and a workaround is https://github.com/ralphbean/taskw/pull/141. At this point I plan to continue using 2.5.1 until there's some movement on one of these issues.
Thought I'd loop in @pjf as he opened that upstream issue.
When you say "a workaround is ralphbean/taskw#141", is that something that we users can do? I have everything installed with homebrew so downgrading isn't a nice clean option.
@robrecord Yeah, it needs to be addressed at the package manager level. I personally can give no guidance on homebrew.
Thank you @ryneeverett. I have uninstalled and built the recommended version from source.
In case it helps anyone else, I found it easier to update the python taskw library to the development version than to downgrade/recompile taskwarrior to the much older 2.5.1; since ralphbean/taskw#147 got merged this works around the issue for now as well.
pip install https://github.com/ralphbean/taskw@develop
Since this is pinned - I'll chime in here that running the above command from @vEnhance is necessary to get compatibility with 2.6.0 release as well:
pip3 install -U https://github.com/ralphbean/taskw@develop
howdy :wave:
got this after upgrading to solve a UUID issue:
and all I can say is: "what?"
Python:
3.9.1
task:2.5.3
bugwarrior:1.8.0
Arch Linux, fully updated.Do I have to nuke my task install or?