-
Notifications
You must be signed in to change notification settings - Fork 26
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 SolidQueue to run a cron job repopulating Location and Observation center_lat/center_lng #2641
Conversation
@JoeCohen @mo-nathan |
I personally would end up routinely ignoring those reports (and the emails
they might generate).
Would other folks review them?
…On Mon, Jan 6, 2025 at 2:27 PM andrew nimmo ***@***.***> wrote:
@JoeCohen <https://github.com/JoeCohen> @mo-nathan
<https://github.com/mo-nathan>
We could run this job silently as I initially set it up, but now it occurs
to me, we'd probably want a real job that counts what it's updating and
logs a report, right?
—
Reply to this email directly, view it on GitHub
<#2641 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAALDFAOPYIHS3BL5FSNJX32JL7NXAVCNFSM6AAAAABUVAP7SCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZUGAZTKNRTGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I don't think it's something that we would review, it's that we'd want a log to know what's been happening in case something went awry. These columns are the key to our being able to switch from obs locations as boxes to obs locations as the center points of boxes that are under a given threshold. Once we're displaying locations like that, we are going to want to know what's happening with these columns. |
Turns out we have ~7876 observations that need updating from this job currently. I guess it should run weekly, if not daily. |
Considering how many obs need updating since our original migration (>20 per day, i'm estimating), and the fact that people will probably want to find recent obs reflected on maps, i've changed the frequency of this job to "nightly". |
Not sure if this config is phrased right, need to do more research. But apparentlythat's all this takes: a config and a command. Update: yes, it is that simple.Also, I'm not sure we need to run it weekly. Monthly might be A-OK. There was some question initially about whether our callbacks would populate these correctly... we should check how many are currently missing in the db.
Responds to #2640