-
Notifications
You must be signed in to change notification settings - Fork 28
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
Make timeseries variable dynamic #1066
Conversation
❌ 1 Tests Failed:
View the top 1 failed tests by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
❌ 1 Tests Failed:
View the top 1 failed tests by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
❌ 1 Tests Failed:
View the top 1 failed tests by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
✅ All tests successful. No failed tests were found. 📣 Thoughts on this report? Let Codecov know! | Powered by Codecov |
https://github.com/codecov/shared/blob/main/shared/django_apps/db_settings.py#L52 Looks like we did this intentionally to defer it to shared. Is that not working? |
You are correct, this also is working. Correct work in this PR codecov/worker#975. Closing this one. |
❌ 1 Tests Failed:
View the top 1 failed tests by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
Purpose/Motivation
What is the feature? Why is this being done?
Seemingly we don't check for timeseries enabled in API while we do so in worker. This has worked so far cause our pods define that variable. This actually reads from your config file and makes it dynamic for people not wanting to opt to the feature.
I defaulted to false but please let me know if that's a wrong assumption.
Links to relevant tickets
codecov/engineering-team#1514