Jan Vlug

I enabled mail in Nextcloud, and nearly all my mail started getting classified as important. Initially, I did not realize that Nextcloud was doing the classification. My preference would be...

See also #1496.

I filled in all mandatory fields. There are no fields with an error message of something red. This issue is about the fact that I do not know which field...

Slightly related to #1457 and [#2700](https://github.com/nextcloud/tasks/issues/2700).

I received a message from *75 at 9:04:27 PM GMT+02:00 that was sent at 5:55:08 PM GMT+02:00. Here is the [debug log](https://debuglogs.org/c4a16c1da84cf5e264191471d926bebbbd1de366fe5019eb5786f830848f019e).

> I may have a related issue. After installing the v1.9.21 rpm with dnf i did not get a desktop entry (KDE, Fedora 42). When trying to run `/opt/bisq/bin/Bisq` manually...

Additional info: After changing the archive state (by archiving or un-archiving, dependent on the Projects initial archive state), Planify could do a full synchronization without errors. I will update this...

Update: I unarchived all Projects, and restarted Planify. Now I get the parser error again. Unfortunately, I cannot figure out what exactly is causing the parser error. However it seems...

I also see this in the logging: ``` (io.github.alainm23.planify:2): libsoup-http2-DEBUG: 17:07:16.490: [CLIENT] [\u001b[31mC12\u001b[00m-\u001b[31mS0\u001b[00m] [-] [RECV] [GOAWAY] Beginning: stream_id=0 (io.github.alainm23.planify:2): libsoup-http2-DEBUG: 17:07:16.490: [CLIENT] [\u001b[31mC12\u001b[00m-\u001b[31mS0\u001b[00m] [-] [RECV] [GOAWAY] Received: stream_id=0, flags=0 (io.github.alainm23.planify:2):...

I did some more testing, and I'm now more convinced that the reception of the GOAWAY is the root cause. I will update the title of this issue accordingly. Maybe...