You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
folder gets removed via Adapter\Smb instead Adapter\Blackhole.
Expected behavior
All actions especially removals executed by SmbScanner must be executed using the Blackhole storage adapter.
This does not work currently as the blackhole adapter is set but each new node load via the vfs does load each parent separately meaning a new parent instance for each load which does not have the previously set blackhole storage adapter set on an another instance of the same node id.
This still leads to folders out of sync: 2019-22-08 07:06:12 [Balloon\Async\SmbScanner,ERROR]: failed sync child node [/Sekretariat] in smb mount [object] (Icewind\SMB\Exception\ForbiddenException(code: 13): Invalid request for /Sekretariat/ABSCHL~1/01AUSZ~1/Wj_2019_20_Noten_N%20S.pdf (ForbiddenException) at /usr/share/balloon/vendor/icewind/smb/src/Exception/Exception.php:30)
It is not exactly clear how folders like "ABSCHL~1" made it into an smblist alongside the original name, those are windows shortcut names visible by executing dir /x on windows.
That said balloon still uses the Adapter\Smb instead Adapter\Blackhole to execute removal operations.
Describe the bug
To Reproduce
db.taskscheduler.jobs.insert({"class" : "Balloon\\Async\\SmbScanner","status" : NumberInt(0),"created" : ISODate("2019-08-20T10:51:22.670Z"),"started" : ISODate("2019-08-19T19:51:23.682Z"),"ended" : ISODate("2019-08-19T19:51:22.670Z"),"worker" : ObjectId("5d5410df2dab1800065a08ce"),"data" : {"id" : ObjectId("5d5bdbb2a85d38000d7af494")},"options" : {"at" : NumberInt(0),"interval" : NumberInt(0),"retry" : NumberInt(0),"retry_interval" : NumberInt(300),"force_spawn" : false,"timeout" : NumberInt(0),"ignore_data" : false}})
Expected behavior
All actions especially removals executed by SmbScanner must be executed using the Blackhole storage adapter.
This does not work currently as the blackhole adapter is set but each new node load via the vfs does load each parent separately meaning a new parent instance for each load which does not have the previously set blackhole storage adapter set on an another instance of the same node id.
Environment
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: