parser error : Extra content at the end of the document

[janvlug]

Describe the bug
When Planify tries to synchronize with Nextcloud, the synchronization fails, and I see this in the log:

(io.github.alainm23.planify:2): libsoup-http2-DEBUG: 22:46:02.712: [CLIENT] [\u001b[36mC23\u001b[00m-\u001b[34mS3\u001b[00m] [READ_DATA] [SESSION] Closed stream 3: NO_ERROR
(io.github.alainm23.planify:2): libsoup-DEBUG: 22:46:02.712: [SESSION QUEUE] [0x561eac2cc670] [RUNNING] run_until_read_done
(io.github.alainm23.planify:2): libsoup-http2-DEBUG: 22:46:02.712: [CLIENT] [\u001b[36mC23\u001b[00m-\u001b[34mS3\u001b[00m] [READ_DATA] Client stream EOF
(io.github.alainm23.planify:2): libsoup-http2-DEBUG: 22:46:02.712: [CLIENT] [\u001b[36mC23\u001b[00m-\u001b[34mS3\u001b[00m] [READ_DATA] [SESSION] State READ_DATA -> READ_DONE
(io.github.alainm23.planify:2): libsoup-http2-DEBUG: 22:46:02.712: [CLIENT] [\u001b[36mC23\u001b[00m-\u001b[34mS3\u001b[00m] [READ_DONE] Finished stream 3: completed
(io.github.alainm23.planify:2): libsoup-DEBUG: 22:46:02.712: [SESSION QUEUE] [0x561eac2cc670] [RUNNING] Message completed
(io.github.alainm23.planify:2): libsoup-DEBUG: 22:46:02.712: [SESSION QUEUE] [0x561eac2cc670] [FINISHING] Processing item, paused=0 state=9
Entity: line 3: parser error : Extra content at the end of the document
}C
^

** (io.github.alainm23.planify:2): WARNING **: 22:46:02.712: Core.vala:257: Failed to sync: .  
(io.github.alainm23.planify:2): libsoup-http2-DEBUG: 22:46:07.631: [CLIENT] [\u001b[36mC23\u001b[00m-\u001b[31mS0\u001b[00m] [-] [RECV] [GOAWAY] Beginning: stream_id=0
(io.github.alainm23.planify:2): libsoup-http2-DEBUG: 22:46:07.631: [CLIENT] [\u001b[36mC23\u001b[00m-\u001b[31mS0\u001b[00m] [-] [RECV] [GOAWAY] Received: stream_id=0, flags=0
(io.github.alainm23.planify:2): libsoup-http2-DEBUG: 22:46:07.631: [CLIENT] [\u001b[36mC23\u001b[00m-\u001b[31mS0\u001b[00m] [-] [RECV] GOAWAY: error=NO_ERROR, last_stream_id=3 timeout
(io.github.alainm23.planify:2): libsoup-http2-DEBUG: 22:46:07.631: [CLIENT] [\u001b[36mC23\u001b[00m-\u001b[31mS0\u001b[00m] [-] [SEND] [GOAWAY]

Note that next to the }C also timeout is mentioned. My Nextcloud is not very powerful, so maybe it might sometimes take some time to process the requests by Planify.

It might be the case that this issue is caused by the content Planify receives from the server. However it seems that Planify stops processing after printing this error. Maybe it would be better to try to continue with other tasks. And maybe it would also be good to give a notification of the encountered error (but that might be a separate feature request).

To Reproduce
Steps to reproduce the behavior:

1. Click the Synchronize button

Desktop (please complete the following information):

• OS or DE: Fedora GNOME Wayland
• Version: 4.14.0