-
Notifications
You must be signed in to change notification settings - Fork 817
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Temporary files break desktop app file synchronization #7776
Labels
Comments
can you share the list of apps installed on your server ? |
Hi, we don’t have any apps. It’s a vanilla install with around 30 users and
400 GB of files.
We have imaginary and clamav installed. What I found odd though, is that
Imaginary has 1000s of threads on the server — albeit only a few of them
using cpu, seems like they are getting stuck and not exiting after
completing the task.
Em seg., 20 de jan. de 2025 às 18:39, Matthieu Gallien <
***@***.***> escreveu:
… can you share the list of apps installed on your server ?
—
Reply to this email directly, view it on GitHub
<#7776 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEVFXIY34XN4M37HKDWV7ML2LVUIXAVCNFSM6AAAAABVRAG6KGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBTGI3DENZUGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
sorry if I was not clear enough |
Hi @mgallien , sorry about that. Here's the output:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug description
Temporary files (starting with special character) breaks file sinchronization on Windows client app when VFS is enabled
This issue appears to be related to #4410
and #4246
Steps to reproduce
Steps to reproduce the behavior:
Expected behavior
A temporary file should not break file synchronization.
Which files are affected by this bug
$CONTROLE DE FATURAMENTO BM07.xlsx
Operating system
Windows
Which version of the operating system you are running.
Windows 11
Package
Official Windows MSI
Nextcloud Server version
29.0.8
Nextcloud Desktop Client version
3.15.3
Is this bug present after an update or on a fresh install?
Fresh desktop client install
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Are you using an external user-backend?
Nextcloud Server logs
Additional info
2025-01-16 11:32:05:583 [ warning nextcloud.sync.vfs.cfapi.wrapper C:\Users\User\AppData\Local\Temp\windows-27802\client-building\desktop\src\libsync\vfs\cfapi\cfapiwrapper.cpp:841 ]: Couldn't set pin state (4) for "C:\Users\Thiarles Porta\Nextcloud\Administrativo\Contratos\656.2023 - (XXXXX)\BOLETINS DE MEDIÇÃO\BM07 JUL-24\
$CONTROLE DE FATURAMENTO BM07.xlsx" with recurse mode 1 : "Identificador inválido."$CONTROLE DE FATURAMENTO BM07.xlsx" to excluded2025-01-16 11:32:05:583 [ warning nextcloud.gui.folder C:\Users\User\AppData\Local\Temp\windows-27802\client-building\desktop\src\gui\folder.cpp:604 ]: Could not set pin state of "Administrativo/Contratos/656.2023 - (XXXXX)/BOLETINS DE MEDIÇÃO/BM07 JUL-24/
[.....]
after this then we start seeing:
2025-01-16 11:37:12:506 [ warning nextcloud.gui.shellextensions.server C:\Users\User\AppData\Local\Temp\windows-27802\client-building\desktop\src\gui\shellextensionsserver.cpp:108 ]: Record not found in SyncJournal for: "Administrativo/Contratos/656.2023 - (XXXXX)/BOLETINS DE MEDIÇÃO/BM06 JUN-24/206_23_FARROUPILHA_SES_.pdf"
2025-01-16 11:37:12:506 [ warning nextcloud.gui.shellextensions.server C:\Users\User\AppData\Local\Temp\windows-27802\client-building\desktop\src\gui\shellextensionsserver.cpp:108 ]: Record not found in SyncJournal for: "Administrativo/Contratos/656.2023 - (XXXXX)/BOLETINS DE MEDIÇÃO/BM06 JUN-24/208_23_RIO_GRANDE_SES_.pdf"
2025-01-16 11:37:12:509 [ warning nextcloud.gui.shellextensions.server C:\Users\User\AppData\Local\Temp\windows-27802\client-building\desktop\src\gui\shellextensionsserver.cpp:108 ]: Record not found in SyncJournal for: "Administrativo/Contratos/656.2023 - (XXXXX)/BOLETINS DE MEDIÇÃO/BM06 JUN-24/206_23_FARROUPILHA_SES_.pdf"
20250116_1046_nextcloud.log.5.zip
The text was updated successfully, but these errors were encountered: