GitLab currently has a limit of 1000 items when listing directories according 
to https://gitlab.com/gitlab-org/gitlab/-/issues/20687.

FWIW, GitHub appears to have a similar limit:

https://github.com/Homebrew/homebrew-core/tree/master/Formula
https://github.com/microsoft/vcpkg/tree/master/ports

I'm not sure if we can do anything about the browsing limit, but you can search 
for a specific file by clicking on "Find file" at the top of the file browser 
screen.

On 9/9/20 12:28 PM, Eugène Adell wrote:
> Hello,
> 
> I have the very same behavior, my browser being Firefox 80.0 (64 bits)
> 
> Le mer. 9 sept. 2020 à 20:44, Maynard, Chris via Wireshark-dev
> <wireshark-dev@wireshark.org> a écrit :
>>
>> It doesn’t seem to be possible to list all dissectors in a web browser 
>> anymore, and those that are listed are populated very slowly.
>> Compare the loading of 
>> https://gitlab.com/wireshark/wireshark/-/tree/master/epan/dissectors with 
>> that of 
>> https://code.wireshark.org/review/gitweb?p=wireshark.git;a=tree;f=epan/dissectors;h=18070dacc9b477c446503e46b68b3c128d1ae984;hb=HEAD.
>>
>> I was interested in looking at packet-ntp.c, but that file never gets 
>> listed, even after clicking “Show more”.   The last file listed for me is 
>> packet-newmail.c. Tested with Firefox 80.0.1 (64-bit) and Chrome Version 
>> 85.0.4183.102 (Official Build) (64-bit).  Of course if you know the 
>> filename, you can click on another file then manually edit the URL with the 
>> file you’re actually interested in looking at, but this isn’t an ideal 
>> solution.
>>
>> Is anyone else experiencing this problem?  And more importantly, is there 
>> anything that can be done to remedy this?
>> Thanks.
>> - Chris
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> CONFIDENTIALITY NOTICE: This message is the property of International Game 
>> Technology PLC and/or its subsidiaries and may contain proprietary, 
>> confidential or trade secret information. This message is intended solely 
>> for the use of the addressee. If you are not the intended recipient and have 
>> received this message in error, please delete this message from your system. 
>> Any unauthorized reading, distribution, copying, or other use of this 
>> message or its attachments is strictly prohibited.
>> ___________________________________________________________________________
>> Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
>> Archives:    https://www.wireshark.org/lists/wireshark-dev
>> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>>              mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
> 

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Reply via email to