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

File tree does not populate sometimes. #67

Open
thockin opened this issue Jun 14, 2019 · 7 comments
Open

File tree does not populate sometimes. #67

thockin opened this issue Jun 14, 2019 · 7 comments

Comments

@thockin
Copy link

thockin commented Jun 14, 2019

Example: https://github.com/kubernetes/kubernetes/pull/73977/commits/7527b3d51a7e996d964dbc5e8a68fe273f23bfdf

(If I don't quote it, github transforms it...weird)

@thockin
Copy link
Author

thockin commented Jun 14, 2019

Another example, this one is only partially populated:

https://github.com/kubernetes/kubernetes/pull/73977/commits/a3817b0d0ff1d58a99322706f49a640e64b823be

@thockin
Copy link
Author

thockin commented Aug 12, 2019

any thoughts on this? Still happening, and makes relying on the file tree hard if I know it is sometimes missing things

@berzniz
Copy link
Owner

berzniz commented Aug 13, 2019

Yes, it is a problem indeed.

The way the extension works is that it reads what's already on the page and creates the tree from that data alone. On very large PRs, Github uses pagination so only after scrolling the data is available.

I don't have a great solution idea (yet), but I wouldn't want to go into the API path (where it'll just read it directly from the GitHub graphql API). If we'll figure out that's the only way, then maybe it will be an optional setting.

I'll be glad to hear more ideas on how this can be resolved.

@RussKie
Copy link

RussKie commented Mar 3, 2020

Here's another one for your collection: dotnet/winforms@034cfd2

Octotree seems to be dealing with the issue by firing multiple requests. To be able to do that and not get rate limited it asks for GitHub PAT.
image

@berzniz
Copy link
Owner

berzniz commented Mar 5, 2020

Thanks for the information. This extension works differently - by only looking at the DOM. This is limiting sometimes, but does not require access tokens to public/private repos.

Open to ideas/PRs for this.

@RussKie
Copy link

RussKie commented Mar 5, 2020

by only looking at the DOM

I suspect at some point DOM changes (i.e. more files become available for browse), but the extension is not catching it.

@RussKie
Copy link

RussKie commented May 12, 2020

I think I found another aspect to this problem.

  • Show all files from all commits - shows all files in the tree
    image
  • Show a selected commit - doesn't show or shows only subset of files
    image

Looking at the Chrome network log - there are no errors, so I don't think it is to do with the GitHub rate limiting, it is probably more to do with information not being retrieved or parsed correctly.

Repro:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants