Hi, fwiw there are actually incompatibilities between nextcloudclient 3.4.1 and nextcloud 23, where some files cant be synced and the client gobbles 100% cpu.
those issues are reported upstream in multiple gh tickets (https://github.com/nextcloud/desktop/issues/4141, https://github.com/nextcloud/desktop/issues/4106 among others for the client, https://github.com/nextcloud/server/issues/29702 and https://github.com/nextcloud/server/issues/30424 for the server), it has something to do with the new 'bulk upload' feature that was added in nextcloud 23. i've locally worked around the issue with a simple ugly patch disabling bulk upload client side, pending resolution/analysis upstream i dunno what should be done with it, but sharing it here.... WFM! Landry c64:/usr/ports/net/nextcloudclient/ $cat patches/patch-src_libsync_capabilities_cpp $OpenBSD$ Index: src/libsync/capabilities.cpp --- src/libsync/capabilities.cpp.orig +++ src/libsync/capabilities.cpp @@ -218,7 +218,7 @@ bool Capabilities::chunkingNg() const bool Capabilities::bulkUpload() const { - return _capabilities["dav"].toMap()["bulkupload"].toByteArray() >= "1.0"; + return false; } bool Capabilities::userStatus() const
