Skip to content

[MIG] Forward-port changes from 14.0 - #2127

Merged
ecino merged 3 commits into
18.0from
18.0-forward-port
Aug 5, 2026
Merged

[MIG] Forward-port changes from 14.0#2127
ecino merged 3 commits into
18.0from
18.0-forward-port

Conversation

@ecino

@ecino ecino commented Aug 5, 2026

Copy link
Copy Markdown
Member

No description provided.

ecino added 3 commits August 5, 2026 08:28
- FIX: Trust the letter's detected language over the field-office stamp; fail safe to translation when it can't be determined
…ion-errors

[T3343] FIX: propagate PG concurrency errors so queue jobs retry
@ecino
ecino merged commit cf43f37 into 18.0 Aug 5, 2026
2 checks passed
@ecino
ecino deleted the 18.0-forward-port branch August 5, 2026 06:33
@greptile-apps

greptile-apps Bot commented Aug 5, 2026

Copy link
Copy Markdown

Confidence Score: 5/5

The reviewed changes are safe to merge.

No defects remain. The tested empty-content paths safely avoid automatic delivery and route correspondence for translation.

Files Needing Attention: No additional files need attention.

T-Rex T-Rex Logs

What T-Rex did

  • I ran the focused executable harness against the language detector and B2S routing for empty text and separator-only text.
  • I verified that the under-50-character guard in advanced_translation/models/langdetect.py short-circuits and returns an empty detector record, so the third-party langdetect call is not reached.
  • I confirmed the harness output shows both inputs queue translations, disable auto-send, and produce no exceptions, with a pass for empty and separator-only cases.

View all artifacts

T-Rex Ran code and verified through T-Rex

Reviews (1): Last reviewed commit: "[MIG] Forward-port changes from 14.0" | Re-trigger Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant