-
-
Notifications
You must be signed in to change notification settings - Fork 316
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
[Bug] FileNotFoundError for addons_paths.json #2706
Comments
Affected is the main branch (8.3.dev) too, but bug does not appear regularly. This may be related to how the number of allowed GitHub API requests is evaluated in CI ENV workflows (number of allowed requests per CI workflow unit or sum of all CI workflows units etc.)
|
Evaluating this again, the issue is 1) the irregular failures and 2) that the result is a traceback. I get the the same for main and for 7.8 branch. The issue number 1 makes the CI much less useful. I may get failures anytime, so I need to manually restart, but additionally I need to restart one by one to avoid another API limit hit. Having the code more forgiving towards rate exceeded, e.g., by more and increasingly longer re-tries might be one way how to cope with that limited resource if we need to keep using it. The issue number 2 seems like an situation not addressed by the code. The rate limit was reached and, at the same time, the file does not exist. As long as there is the dependence on something with a rate limit, we need a really good message to tell what happened. |
Describe the bug
I get traceback with
FileNotFoundError: [Errno 2] No such file or directory: '/home/runner/.grass7/addons/addons_paths.json'
when rate limit is exceeded to access GitHub.To Reproduce
Rate limit related, so hard to reproduce. The command was:
Expected behavior
No traceback, maybe an error message.
Screenshots
Output:
System description (please complete the following information):
Additional context
I did not investigate if this is applicable to v8.
The text was updated successfully, but these errors were encountered: