mirror of
https://github.com/discourse/discourse.git
synced 2026-08-06 13:08:40 +08:00
5b6d87a4c9Previously, every SQL query finding translation candidates (admin progress report and backfill jobs) filtered on `LENGTH(posts.raw)`, which forced detoasting `raw` for every scanned row and made those queries slow, while the limit itself no longer guarded anything — long posts are already split into chunks sized to the model's `max_output_tokens`, and core's `max_post_length` bounds raw size. This change removes the setting and its query filters, deletes any stored override via a post-deploy migration, and bumps the translation progress cache versions since eligibility counts change. Note for review: on existing sites, posts previously excluded by the limit become eligible for backfill, so pending counts (and translation spend on long-form content) will increase accordingly. |
||
|---|---|---|
| .. | ||
| 20260205065417_drop_tool_details_from_ai_personas.rb | ||
| 20260206013737_migrate_existing_secrets_to_ai_secrets.rb | ||
| 20260306000002_finalize_ai_agents_schema.rb | ||
| 20260701013609_drop_ai_agent_fixed_limit_columns.rb | ||
| 20260715090434_drop_ai_post_image_descriptions.rb | ||
| 20260721080420_backfill_ai_summary_locales.rb | ||
| 20260721080424_remove_locale_agnostic_ai_summaries_index.rb | ||
| 20260728045008_remove_ai_translation_backfill_max_age_setting.rb | ||
| 20260729153343_remove_ai_translation_max_post_length_setting.rb | ||
