Steven R. Loomis
Steven R. Loomis
here is the raw comment content per jira ```json {"body":{"version":1,"type":"doc","content":[{"type":"paragraph","content":[ {"type":"text","text":"These may be variants of: "}, {"type":"hardBreak"}, {"type":"text","text":"U+26911 \uD85A\uDD11"}, {"type":"hardBreak"}, {"type":"text","text":"U+2690E \uD85A\uDD0E"}, {"type":"hardBreak"},{"type":"text","text":"U+76A1 皡"}, {"type":"hardBreak"},{"type":"text","text":"U+76A5 皥"}, {"type":"hardBreak"},{"type":"text","text":"U+76B7 皷"}]} ```
It is definitely corrupt in taskwarrior
- so sadly this is not somehow fixed by task 2.6.0 + develop branch of taskw. bUt i'll try deleting the tasks (by UUID) and trying again.
- issue still there after deletion and re-pull of tasks.
Still present with taskwarrior v2.6.2
I'm now seeing the same for Github as well > INFO:bugwarrior.db:Updating task bc317b67-5a4d-432d-adc2-0690a3ddfbb6, (bw)Is#7042 - feat: LDML Keyboard Support 🙀 .. https://github.com/keymanapp/keyman/issues/7042; githubtitle: 'feat: LDML Keyboard Support ������' -> 'feat:...
@AugustinMauroy i'll take a look.
100%. in fact, i just stumbled on an old version of the homepage promoting "Node 18" by searching for "Node Release Cycle"
@targos have not heard of this, may be good to file an ICU bug upstream at https://unicode-org.atlassian.net // @jefgen
may have to fall back to `.c` file builds for data if the assembly generayion is getting confused