2024-07-02 08:51:59 -07:00
|
|
|
# frozen_string_literal: true
|
|
|
|
|
|
|
|
|
|
class AiTopicSummarySerializer < ApplicationSerializer
|
2024-07-31 15:21:26 -03:00
|
|
|
attributes :summarized_text,
|
|
|
|
|
:algorithm,
|
|
|
|
|
:outdated,
|
|
|
|
|
:can_regenerate,
|
|
|
|
|
:new_posts_since_summary,
|
|
|
|
|
:updated_at
|
2024-07-02 08:51:59 -07:00
|
|
|
|
|
|
|
|
def can_regenerate
|
2024-07-04 10:48:18 +10:00
|
|
|
scope.can_request_summary?
|
2024-07-02 08:51:59 -07:00
|
|
|
end
|
|
|
|
|
|
|
|
|
|
def new_posts_since_summary
|
FIX: Make summaries backfill job more resilient. (#1071)
To quickly select backfill candidates without comparing SHAs, we compare the last summarized post to the topic's highest_post_number. However, hiding or deleting a post and adding a small action will update this column, causing the job to stall and re-generate the same summary repeatedly until someone posts a regular reply. On top of this, this is not always true for topics with `best_replies`, as this last reply isn't necessarily included.
Since this is not evident at first glance and each summarization strategy picks its targets differently, I'm opting to simplify the backfill logic and how we track potential candidates.
The first step is dropping `content_range`, which serves no purpose and it's there because summary caching was supposed to work differently at the beginning. So instead, I'm replacing it with a column called `highest_target_number`, which tracks `highest_post_number` for topics and could track other things like channel's `message_count` in the future.
Now that we have this column when selecting every potential backfill candidate, we'll check if the summary is truly outdated by comparing the SHAs, and if it's not, we just update the column and move on
2025-01-16 09:42:53 -03:00
|
|
|
object.target.highest_post_number.to_i - object.highest_target_number.to_i
|
2024-07-02 08:51:59 -07:00
|
|
|
end
|
|
|
|
|
end
|
