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
Starting with Cyberduck 7.1.0, I've noticed that when connecting to a private S3 compatible storage service, I can no longer list files in a directory where there are over 1000 files/keys present. The UI presents itself as if there were no files in the directory.
In Cyberduck 7.0.2, executing the same scenario results in displaying the >1000 list of keys.
When turning on debugging, I see the following:
> GET /bucket/?encoding-type=url&max-keys=1000&prefix=path%2Fto%2Flarge%2Fdirectory%2F&delimiter=%2F HTTP/1.1
This returns a 200.
I also see
> GET /bucket/?encoding-type=url&max-keys=1000&prefix=path%2Fto%2Flarge%2Fdirectory%2F&delimiter=%2F&marker=path%2Fto%2Flarge%2Fdirectory%2Fmarker.json HTTP/1.1
This also returns a 200.
Then I see the following
2020-03-17 13:00:23.199539-0400 0x7427b8 Default 0xaecc6e 88140 0 Cyberduck: (libcore.dylib) [ch.sudo.cyberduck:Thread-40 ch.cyberduck.core.threading.BackgroundCallable] Failure java.lang.IllegalArgumentException: URLDecoder: Illegal hex characters in escape (%) pattern - Error at index 1 in: "ap" running background task
java.lang.Exception
at ch.cyberduck.core.threading.BackgroundCallable.<init>(BackgroundCallable.java:36)
at ch.cyberduck.core.threading.DefaultBackgroundExecutor.execute(DefaultBackgroundExecutor.java:67)
at ch.cyberduck.core.AbstractController.background(AbstractController.java:71)
at ch.cyberduck.ui.cocoa.controller.BrowserController.reload(BrowserController.java:517)
at ch.cyberduck.ui.cocoa.controller.BrowserController.setWorkdir(BrowserController.java:3064)
at ch.cyberduck.ui.cocoa.controller.BrowserController.setWorkdir(BrowserController.java:3039)
at ch.cyberduck.ui.cocoa.controller.BrowserController.insideButtonClicked(BrowserController.java:2705)
at ch.cyberduck.ui.cocoa.controller.BrowserController$AbstractBrowserTableDelegate.tableRowDoubleClicked(BrowserController.java:3597)
at java.base/jdk.internal.reflect.NativeMethodAccessorI
2020-03-17 13:00:23.199617-0400 0x7427b8 Info 0xaecc6e 88140 0 Cyberduck: (libcore.dylib) [ch.sudo.cyberduck:Thread-40 ch.cyberduck.core.threading.SessionBackgroundAction] Run alert callback ch.cyberduck.ui.cocoa.callback.PromptAlertCallback@8102284 for failure BackgroundException{class=class ch.cyberduck.core.exception.ConnectionCanceledException, file=null, message='Error', detail='Unknown application error. URLDecoder: Illegal hex characters in escape (%) pattern - Error at index 1 in: "ap".', cause='java.lang.IllegalArgumentException: URLDecoder: Illegal hex characters in escape (%) pattern - Error at index 1 in: "ap"'}
I'm having issues building Cyberduck on macOS 10.15.3 (most likely due to my own incompetence) so I can't quite debug the exact issue. If I can figure that out, I can attempt to create a patch fixing or working around my issue.
Reading through code, I think it may be related to 07e0e54.
I'm not blocked since I have a work around (using 7.0.2) but figured that I might create a ticket for this anyway to track.
The text was updated successfully, but these errors were encountered:
Can you please test with the latest snapshot build 7.3.1.32695.
Yes. I tested it on Version 7.3.1 (32695) and the directory with >1000 keys in it returned all the files under it.
Are there other scenarios you would like me to verify in this build for this fix?
Starting with Cyberduck 7.1.0, I've noticed that when connecting to a private S3 compatible storage service, I can no longer list files in a directory where there are over 1000 files/keys present. The UI presents itself as if there were no files in the directory.
In Cyberduck 7.0.2, executing the same scenario results in displaying the >1000 list of keys.
When turning on debugging, I see the following:
I also see
This also returns a 200.
Then I see the following
I'm having issues building Cyberduck on macOS 10.15.3 (most likely due to my own incompetence) so I can't quite debug the exact issue. If I can figure that out, I can attempt to create a patch fixing or working around my issue.
Reading through code, I think it may be related to 07e0e54.
I'm not blocked since I have a work around (using 7.0.2) but figured that I might create a ticket for this anyway to track.
The text was updated successfully, but these errors were encountered: