Skip to content
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

Folder listing incomplete in browser when expanding a folder #9583

Closed
cyberduck opened this issue Jun 5, 2016 · 11 comments
Closed

Folder listing incomplete in browser when expanding a folder #9583

cyberduck opened this issue Jun 5, 2016 · 11 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jun 5, 2016

2702f66 created the issue

Hi,

First of all, congratulations for the great piece of software Cyberduck you have built :) This is a great job !

I've just decided to create a ticket for the following issue because I've noticed that it hasn't been fixed during the multiple releases so far. Maybe no one else is affected but I can't really imagine it...

The issue is simple. After the connection is successfull, the view with all the files/folders is cut as soon as I expand a folder. There is one condition for this bug to happen: there must be enough files/folders to fill all the view and make a scrollbar appear.

For example, let's consider that I have 1 folder with 300 files inside on my server. First, I'm connecting to my server via Cyberduck and I see my folder closed. This is ok but now I want to expand it. So I click on the little horizontal arrow in front of it but only the 20 first files are shown (20 is an example to say that not all of them are shown) because I would need to scroll down to view the others. So far so good, except that the other files are not shown when I scroll down (the listing is cut by Cyberduck). When it happens, I need to close my folder and re-expand it, then I can scroll down and see all the 300 different files.

Thank you for your help and debugging.
Laurent

Below is the result of the log drawer because you ask for it. This is different from my example but the issue is the same: the listing is cut after wp-config-sample.php in the visual interface whereas it is complete in the log drawer:

CWD /www
250 OK. Current directory is /www
TYPE A
200 TYPE is now ASCII
PASV
227 Entering Passive Mode (213,186,33,206,127,158)
MLSD
150 Accepted data connection
type=cdir;sizd=27;modify=20160506195840;UNIX.mode=0705;UNIX.uid=87078;UNIX.gid=100;unique=100001gd81ba0; .
type=pdir;sizd=9;modify=20150910175738;UNIX.mode=0705;UNIX.uid=87078;UNIX.gid=100;unique=100001gd81b9c; ..
type=file;size=12140;modify=20160413081053;UNIX.mode=0644;UNIX.uid=87078;UNIX.gid=100;unique=100001g95b1862; .htaccess
type=file;size=176;modify=20140603220146;UNIX.mode=0604;UNIX.uid=87078;UNIX.gid=100;unique=100001gba80df; favicon.ico
type=file;size=53;modify=20140323221508;UNIX.mode=0604;UNIX.uid=87078;UNIX.gid=100;unique=100001g30a2b47; google06947efbdfe73f48.html
type=file;size=418;modify=20141218212259;UNIX.mode=0644;UNIX.uid=87078;UNIX.gid=100;unique=100001gd81ba2; index.php
type=file;size=19935;modify=20160413080628;UNIX.mode=0644;UNIX.uid=87078;UNIX.gid=100;unique=100001gd81ba4; license.txt
type=dir;sizd=18;modify=20160605100732;UNIX.mode=0705;UNIX.uid=87078;UNIX.gid=100;unique=100001ga416f8a; logs_backwpup
type=file;size=7360;modify=20160506195840;UNIX.mode=0644;UNIX.uid=87078;UNIX.gid=100;unique=100001gd81bae; readme.html
type=file;size=237;modify=20140413083706;UNIX.mode=0604;UNIX.uid=87078;UNIX.gid=100;unique=100001ga001e11; robots.txt
type=file;size=5032;modify=20160413080628;UNIX.mode=0644;UNIX.uid=87078;UNIX.gid=100;unique=100001gd81bad; wp-activate.php
type=dir;sizd=90;modify=20160413080627;UNIX.mode=0705;UNIX.uid=87078;UNIX.gid=100;unique=100001gd81e64; wp-admin
type=file;size=364;modify=20160413080628;UNIX.mode=0644;UNIX.uid=87078;UNIX.gid=100;unique=100001gd81ba9; wp-blog-header.php
type=file;size=1476;modify=20160413080628;UNIX.mode=0644;UNIX.uid=87078;UNIX.gid=100;unique=100001gd81ba8; wp-comments-post.php
type=file;size=3568;modify=20160413080628;UNIX.mode=0644;UNIX.uid=87078;UNIX.gid=100;unique=100001gd81baa; wp-config-sample.php
type=file;size=3493;modify=20141201185634;UNIX.mode=0400;UNIX.uid=87078;UNIX.gid=100;unique=100001g17238b67; wp-config.php
type=dir;sizd=12;modify=20160604205618;UNIX.mode=0705;UNIX.uid=87078;UNIX.gid=100;unique=100001gd81ffd; wp-content
type=file;size=3286;modify=20150831141252;UNIX.mode=0644;UNIX.uid=87078;UNIX.gid=100;unique=100001gd81bab; wp-cron.php
type=dir;sizd=162;modify=20160413080628;UNIX.mode=0705;UNIX.uid=87078;UNIX.gid=100;unique=100001gd81baf; wp-includes
type=file;size=2380;modify=20141218212259;UNIX.mode=0644;UNIX.uid=87078;UNIX.gid=100;unique=100001gd81ba6; wp-links-opml.php
type=file;size=3316;modify=20151212213332;UNIX.mode=0644;UNIX.uid=87078;UNIX.gid=100;unique=100001gd81ba3; wp-load.php
type=file;size=33837;modify=20160413080628;UNIX.mode=0644;UNIX.uid=87078;UNIX.gid=100;unique=100001gd82b2c; wp-login.php
type=file;size=7887;modify=20151212213332;UNIX.mode=0644;UNIX.uid=87078;UNIX.gid=100;unique=100001gd81e63; wp-mail.php
type=file;size=13106;modify=20160413080628;UNIX.mode=0644;UNIX.uid=87078;UNIX.gid=100;unique=100001gd81bac; wp-settings.php
type=file;size=28624;modify=20160413080628;UNIX.mode=0644;UNIX.uid=87078;UNIX.gid=100;unique=100001gd81ba1; wp-signup.php
type=file;size=4035;modify=20141218212259;UNIX.mode=0644;UNIX.uid=87078;UNIX.gid=100;unique=100001gd81ba5; wp-trackback.php
type=file;size=3061;modify=20151212213332;UNIX.mode=0644;UNIX.uid=87078;UNIX.gid=100;unique=100001gd81ffc; xmlrpc.php
226-Options: -a -l 
226 27 matches total
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 8, 2016

@dkocher commented

I have never seen this bug myself. Can you find any related output in the system.log (/Applications/Utilities/Console.app)?

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 13, 2016

7ffc8bb commented

I have the same problem. Appears only as parts of the listing are not visible, because the listing is longer than the viewport. As soon as you open a subfolder with more content the none visible content has to be reloaded to be accessible when scrolling down. Have not found any related output at system.log. The bug existed also with older versions.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 27, 2016

@dkocher commented

I cannot reproduce the issue here. Are you using the latest version of Cyberduck?

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 27, 2016

7ffc8bb commented

I'm using Version 5.0.9 (20675) on OSX 10.11.6. Error happened with most of the previous versions.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 29, 2016

2702f66 commented

Hi,

I can confirm that v5.0.9 (20675) has still the issue.
More, as requested, you may find below the related output in Console:

29/07/2016 16:18:43,789 Cyberduck[22189]: NSWindow warning: adding an unknown subview: <NSButton: 0x7fcc19ecc350>. Break on NSLog to debug.
29/07/2016 16:18:43,790 Cyberduck[22189]: Call stack:
(
	0   AppKit                              0x00007fff8f1127b7 -[NSThemeFrame addSubview:] + 107
	1   libjnidispatch.dylib                0x0000000127468134 ffi_call_unix64 + 76
	2   ???                                 0x00007fff52cf3518 0x0 + 140734582699288
)

I hope it helps :)
Best regards,
JL

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 17, 2016

@dkocher commented

Replying to [comment:7 lofaro]:

Hi,

I can confirm that v5.0.9 (20675) has still the issue.
More, as requested, you may find below the related output in Console:

29/07/2016 16:18:43,789 Cyberduck[22189]: NSWindow warning: adding an unknown subview: <NSButton: 0x7fcc19ecc350>. Break on NSLog to debug.
29/07/2016 16:18:43,790 Cyberduck[22189]: Call stack:
(
	0   AppKit                              0x00007fff8f1127b7 -[NSThemeFrame addSubview:] + 107
	1   libjnidispatch.dylib                0x0000000127468134 ffi_call_unix64 + 76
	2   ???                                 0x00007fff52cf3518 0x0 + 140734582699288
)

I hope it helps :)
Best regards,
JL

This warning got fixed in 94c64ab. See #9554.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 8, 2016

7ffc8bb commented

I think this is fixed now: Version 5.2.2 (21483)

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 8, 2016

@dkocher commented

As I could never reproduce this issue here I will close it. Please reopen if you encounter this bug again.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 8, 2016

2702f66 commented

Replying to [comment:9 dbleisch]:

I think this is fixed now: Version 5.2.2 (21483)

Hello,

I've just tested with version 5.2.2 and I can confirm this is NOT fixed.
The issue is still the same. I reopen this ticket then.

Best regards,

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 16, 2017

@dkocher commented

Please reopen this issue if you can still reproduce with the current 5.3 snapshot build.

Loading

@cyberduck cyberduck closed this Jan 16, 2017
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 26, 2017

2702f66 commented

A priori, I cannot reproduce the problem with Cyberduck 5.3.3 (23221). Can you confirm that you changed something?
Thank you.

Loading

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants