-
Notifications
You must be signed in to change notification settings - Fork 86
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
Use exponential backoff when retrying with tenacity #396
Comments
Hello, I'm writing on behalf of my team. We wish to work on this issue as a part of our coursework for our University, and are missing the secret required to run the project locally. We'd like to work with you to help fix this issue. |
Hello, this project is unfortunately not as documented as it should to onboard new contributors. You could do the necessary changes without running the full bot, instead relying on unit tests. That's not ideal, nor the easiest path, but doable. Another idea if you're willing to contribute to the project would be to add support for a local configuration file in the bot. I've filed a new issue to track this: #437 Also, if you're willing to invest even more time, we obviously need some documentation for the bot aimed at developers: #438 |
Is there anything we can look at to better understand how to run the project locally? As we understand, we need the backend to run in order to work on the frontend, and the backend currently isn't working for us due to the missing access to the secret using the As for the bot, when we try to run it, we keep encountering the CCing @harsh6646, @gagankbl, @KostyaIliouk, @alexeicoreiba |
Hello @KohilanMohanarajan , I've added some more infos on the setup of the different projects in this PR. Once merged, you'll be able to skip the taskcluster secret part. You can reach us directly on our Matrix instance in the code coverage channel. |
We've introduced usage of tenacity in #366, but we're using normal retries. It'd be nicer to have exponential backoff.
The text was updated successfully, but these errors were encountered: