Log message incorrectly referenced a set schedule
This log line claims that things are being refreshed at 1am CDT when the interval is configurable
https://github.com/chaoss/augur/blob/0c57454a27f298d67d8d61f5d78250d2127b540e/augur/tasks/init/celery_app.py#L245
- [ ] confirm what time, if any, this job runs, or if its likely to be relative to when augur starts up
- [ ] confirm whether augur is using the system timezone
- [ ] update the log message to specify the correct number of days and either remove or print the correct timezone dynamically
Hey i would like to pick this up !
Hey i would like to pick this up !
if you feel strongly about it, sure. Although I think this is harmless enough and simple enough that it may be better to leave to someone who is brand-new to contributing to the repo
Got it, totally understand I’ll leave this one open for a new contributor then! I can pick some other issue .
@MoralCode I have this solution for the issue, if you suggest I can open a PR else leaving it to someone else.
Thats nice of you to propose a solution! I still think this is a great issue to leave open so a first-timer can give contributing a try.
That said, it seems like you already did the work, so id say its up to you if you want to submit it as a PR or or not.
Thats nice of you to propose a solution! I still think this is a great issue to leave open so a first-timer can give contributing a try.
That said, it seems like you already did the work, so id say its up to you if you want to submit it as a PR or or not.
Ok, leaving for any first-timer!
@MoralCode Hey! I’m a first-time contributor and I’d love to take this issue up. Could you please assign it to me?
@MoralCode Hey! I’m a first-time contributor and I’d love to take this issue up. Could you please assign it to me?
I think you should open a PR, don't worry much about assigning!
@MoralCode Hey! I am a first timer and I,d like to take this issue up. Could you Please Assign It to me??
@KariraLakshya there are already three (two open, one closed) PRs linked to this issue.
I'd be happy to chat about this in more detail over on the CHAOSS Slack in the #wg-augur-8knot channel if you'd like help finding other "good first issues" that you can get started with
@MoralCode Hi! I’m new here and would love to contribute to this issue alongside others. Could you please assign me as well? I’ll work on it with full enthusiasm and open a draft PR soon.
@MoralCode Hi! I’m new here and would love to contribute to this issue alongside others. Could you please assign me as well? I’ll work on it with full enthusiasm and open a draft PR soon.
There are already three (two open, one closed) PRs linked to this issue.
I'd be happy to chat about this in more detail over on the CHAOSS Slack in the #wg-augur-8knot channel if you'd like help finding other "good first issues" that you can get started with.
Due to the number of duplicate requests to work on this issue, I am going to lock this issue to limit discussion to augur maintainers.
If you would like to work on this issue, please check out the other issues tagged "good first issue" that are not already being worked on. If there are no good first issues you would like to work on, you can also try running augur (using either the docker compose workflow, or the manual setup form the docs) to help us report and fix issues you identify with either the documentation or the application itself.