README not loading due to file pagination

In some of the projects Readme file is not loading and the "No Readme" Error is shown instead. It's probably with the private repositories.

I have also cross checked the Readme file on the Gitlab website, and it's shown there. Also, in the files tab of the app Readme file is not there.

changed the description

changed the description

added Bug label

@RodWizard Whoops, sorry... I accidentally reverted your edit by adding that tag...

I've had this problem too.

Just found out the problem. App is not showing Readme if the file is spelled in all lower case like "readme.md" but showing it if it's spelled in all caps like "README.md".

changed the description

@nprail no problem, edited it again.

I am not too sure that the case matters. Looking through the code there, the casing is ignored. I think it could be that it occurs on projects that do not have a default branch set. Is this the case for your project?

I have 5 private repository.

• All of them have a default branch set to master.
• 4 of them have a readme file.
• Two of which have the readme file named README.md (App is showing their readme).
• The other two have the readme file name readme.md (App is showing no readme error)

Just found out that LabCoat is not showing the full list of files in the root directory. And the Readme file is also for that reason is not shown. Screenshots are attached 😀

List of files on GitLab.com

List of Files on LabCoat

After License.txt no other file is loaded, and readme.md (which I changed it to README.md) is just after that.

@RodWizard I have at least two private projects in which the README.md is all caps and it doesn't load. Capitalization doesn't seem to be the problem. That's strange that it stops loading after the LICENSE.txt. Is the file that it stops loading at in the same position in each repo?

Ah yeah I think the issue is probably that they made this endpoint paginated with API v4. It did not used to be paginated, and calling to the root would list out all files and folders. We probably need to modify this to where we either search for a README file at the root if that is supported, or continuously load the files with pagniation until we find the README or reach the end.

Oh, that makes sense. I'll assign myself to this since I did the v4 switch.

assigned to @nprail

added To Do label

@nprail yeah, both are based on a framework and thus both are at the same position in each repo.

@Jawnnypoo Yeah, the API update makes sense. This might be the problem.

changed title from Latest Update Bug: Readme Not loading in some projects. to README not loading due to file pagination

@Jawnnypoo Should I just make the per_page count something REALLY high so that it always loads all the files?

mentioned in commit 0963eb28

Yep, that makes sense

closed

I guess the max is 100

Ahh, you are right. Do we think that is enough? Hopefully. Can you change this to reflect that @nprail ? Maybe make it a constant somewhere in case we run into something like this again

I had changed the max to 1000. I guess it rounds down to 100. I'll switch it to 100 and make it a constant (once I figure out how 😉).

Heh, const val. Within GitLabService, next to API_VERSION would be great

I just figured that out 😄

7f5fdc6d

When will it be released?

Any release date decided yet? @Jawnnypoo @nprail

mentioned in issue #296 (closed)

I'm not able to do a release. @Jawnnypoo?

@Jawnnypoo please release fast as my project is on beta test and I am unable control it via app.

mentioned in issue #305 (closed)