-
Notifications
You must be signed in to change notification settings - Fork 80
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
Comments
Another example, this one is only partially populated:
|
any thoughts on this? Still happening, and makes relying on the file tree hard if I know it is sometimes missing things |
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. |
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. |
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. |
I suspect at some point DOM changes (i.e. more files become available for browse), but the extension is not catching it. |
I think I found another aspect to this problem.
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:
|
Example:
https://github.com/kubernetes/kubernetes/pull/73977/commits/7527b3d51a7e996d964dbc5e8a68fe273f23bfdf
(If I don't quote it, github transforms it...weird)
The text was updated successfully, but these errors were encountered: