Skip to content
This repository was archived by the owner on Jul 22, 2025. It is now read-only.

Conversation

@romanrizzi
Copy link
Member

No description provided.

@xfalcox
Copy link
Member

xfalcox commented Oct 23, 2024

From what I understood here, this will trigger on every new post and then update the gist if the topic has a hot score even if it was years ago?

Maybe we can check for a recent hot score on the topic before enqueuing the job?

@romanrizzi
Copy link
Member Author

@xfalcox - Good point, but I think what we want is a min score? We have a gravity setting that bring scores down over time

@xfalcox
Copy link
Member

xfalcox commented Oct 23, 2024

@xfalcox - Good point, but I think what we want is a min score? We have a gravity setting that bring scores down over time

Since this is the fast track and anything we miss will be auto-healed by the other job, IMO we can be pretty selective and only fast-track hot-scores updated recently. I'd go with updated in the last day to start.

@romanrizzi
Copy link
Member Author

LGTM 👍

@xfalcox xfalcox merged commit a2b1ea3 into main Oct 25, 2024
5 checks passed
@xfalcox xfalcox deleted the fast_gist_regen branch October 25, 2024 15:38
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants