Annotation with slashes sync problem crashes taskwarrior
See original GitHub issueI added a url (http://…) to a task as a annotation. After changing and syncing the task with foreground Taskwarrior crashed. After debugging it a little bit I found out that foreground converted http:\/\/
to http:\\\\
. This seems to happen only with annotations.
Issue Analytics
- State:
- Created 5 years ago
- Comments:13 (6 by maintainers)
Top Results From Across the Web
Troubleshooting Sync - Taskwarrior
Here is a list of problems you may encounter, with the most common ones listed first. The single most common problem has been...
Read more >Terminology - Taskwarrior
annotation. An annotation is a note added to an existing task, and is in the form of a text string. There can be...
Read more >Taskwarrior Configuration — Generic service & computer ...
Taskwarrior Configuration . Installation . Install base packages and setup environment redirection. . apt install taskwarrior timewarrior libjson-perl.
Read more >https://es.tldp.org/mirror/OpenBSD/Changelogs/Chan...
70.html Log message: sync package versions CVSROOT: /cvs Module name: www ... Fixes a crash reported by martijn@ when a session with multiple...
Read more >suse.uni-leipzig.de/pub/ftp.opensuse.org/opensuse/...
+ Fix several GObject introspection annotations. + Update user agent quiks to fix Outlook.com and Chase.com. + Fix several crashes and rendering issues....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Good news! I think I’ve finally managed to fix this bug. I have the work pushed to the
annotation-slashes
branch now and if everything goes smoothly it will be going out in the next Foreground release (most likely a minor version with this fix and some Play Store housekeeping).I would be very appreciative if someone could pull down that branch and do some additional testing to make sure it’s fixed and that no other breakages happened.
I just released Foreground 1.5.2 which includes the fix for this issue. It’s available now via the Releases tab and it’s rolling out through Google Play and F-Droid.