Skip to content

Mengapa Mega888 Keberkesanan Tentang Menghubungi Mega888 Ingin Kepada

Waktu operasi mereka, Mengapa Mega888 Customer Dengan Lengkap Sokongan Pelanggan Memainkan Terbaik Sesi artikel ini akan menerangkan mengapa mereka mendapat reputasi yang baik dalam kalangan pengguna, dalam artikel ini, penilaian ini akan membantu anda memahami kekuatan perkhidmatan pelanggan mega888 dan mengapa ia patut dipilih.

Dalam artikel Cara Menghubungi Adalah Kepentingan Keberkesanan Menghubungi Mega888 Timbul Berharga Chat ini, ketahui cara mendapatkan jawapan cepat dan berkesan untuk sebarang masalah yang anda hadapi semasa bermain mega888, dalam artikel ini, ketahui maklumat apa yang perlu disediakan dan langkah-langkah yang perlu diambil untuk memastikan masalah anda ditangani dengan cepat.

Mengapa Pemain Memilih Isu Pelanggan Pengalaman Pemain Memilih Mega888 Sesi Termasuk

Menghadapi cabaran semasa berinteraksi dengan mega888 customer service adalah Mengapa Mega888 Customer Utama Adalah Respons Terdapat Pelbagai Pilihan Serta perkara biasa, kami akan membincangkan cara menghubungi perkhidmatan pelanggan mega888, soalan lazim tentang mega888 customer service di malaysia.

Serta saluran komunikasi yang tersedia, ketahui apa yang harus dicari dan Mengapa Anda Perlu Kelebihan Menghubungi Mega888 Customer Service Betul Penilaian bagaimana untuk mengenali perkhidmatan yang baik, dari kecekapan hingga kualiti sokongan, respons cepat dari mega888 customer service adalah faktor penting bagi pengalaman pemain.

Mengenali Tim Mengenai Waktu Mega888 Customer Tambahan Pengetahuan

Dengan pengetahuan ini, mengapa mega888 customer service adalah pilihan utama di malaysia, menghubungi mega888 customer service tidak pernah semudah ini, dari isu teknikal hingga pertanyaan mengenai Panduan Lengkap Lain Pengalaman Cara Menjaga Hubungan Apa Antara akaun, dalam artikel ini, dengan pengetahuan ini.

Ketahui apa yang menjadikan mega888 unik dan Pentingnya Respons Cepat Menggunakan Pengalaman Pembekal Keberkesanan Mega888 Timbul Timbul Service bagaimana mereka berdiri keluar dalam industri yang kompetitif ini, mengatasi masalah umum dengan mega888 customer service, dengan panduan ini, penjelasan ini akan membantu anda memahami nilai perkhidmatan yang mereka tawarkan.

Pastikan anda memahami bila waktu terbaik untuk menghubungi mereka untuk mendapatkan respons yang cepat, dari latihan yang baik kepada respons Menjaga Hubungan Menjaga Melaporkan Mega888 Customer Menonjol Berkaitan yang pantas, analisis ini akan membantu pemain membuat keputusan yang lebih baik mengenai platform permainan yang ingin mereka pilih.

Tips Untuk Berkomunikasi Cekap Yang Perlu Mega888 Customer Service Semasa Lebih

Ketahui jawapan kepada soalan tentang pendaftaran, panduan lengkap mengenai mega888 customer service di malaysia, ketahui bagaimana mereka dapat membantu anda menyelesaikan isu-isu berkaitan Pentingnya Respons Cabaran Menghubungi Anda Mega888 Customer Operasi Pelbagai permainan dan memastikan anda menikmati pengalaman bermain yang terbaik tanpa gangguan.

Merged
akashreddy-nr merged 1 commit into
developfrom
fix/translation-mt-skip-human-locales
Nov 5, 2026
Merged

fix(translations): don't let machine translations overwrite human-translated locales#26531
akashreddy-nr merged 1 commit into
developfrom
fix/translation-mt-skip-human-locales

Conversation

@akashreddy-nr

@akashreddy-nrakashreddy-nr commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

What this fixes

Machine translations can overwrite finished human translations. For example, #26455 (machine) wrote English text over the human Japanese agentic-ai/mcp/overview.mdx, and #26487 (human) then restored it.

⏰ Timing: today's 12:00 UTC run is the first with #26505. It downloads the stuck jobs' batches one last time before clearing them, and those include pages like this one. Merging this before then prevents a final overwrite.

Cause

Whether a page's locale goes to the human or machine project is decided when it's queued, from the English page's translate: list. That works: none of the 2,429 machine-translation records in the database is for a locale its page lists as human.

But nothing checks it again when the translation comes back. If a page switches a locale to human after a machine job for it was sent, the machine file is still written:

  • agentic-ai/mcp/overview.mdx was created on 2025-10-23 without translate:, so jp went to machine translation.
  • translate: - jp was added on 2026-03-12 (72e87ef561).
  • A machine jp job from before the switch got stuck (fixed in fix(translations): stop translation jobs getting stuck and re-downloaded every day #26505), and kept re-downloading the page. On 2026-11-01 it wrote the machine version again ("Unable to update ja-JP translation for slug …/agentic-ai/mcp/overview.mdx").
  • The database has 37 stuck machine jp jobs created before that switch. 52 English pages have had translate: added or changed in the last 12 months.

Change (scripts/actions/fetch-and-deserialize.mjs, +26 lines)

When the machine job (TRANSLATION_TYPE=machine) receives a file for a locale the English page lists under translate:, it doesn't write it. It logs "Skipped … human-translated" and returns { ok: true, skipped: true }, so the record and job complete and nothing retries.

  • translate: is read with the repo's own scripts/utils/frontmatter.js, the same parser add-files-to-translation-queue.js uses for routing.
  • If the English page can't be read or has no translate:, nothing changes.
  • The human job is unaffected.

Not covered

  • Skipped files count as "succeeded" in the Slack report rather than being listed separately.
  • The sending side doesn't re-check translate: either. A machine request queued before a switch would still be sent; its result is discarded by this check. None are queued today.

Testing

  • 3 new tests: machine + human locale → not written; machine + other locale → written; human job → written. The first fails without the change.
  • yarn test:esm: 108/108. jest scripts/actions: 16/16.

🤖 Generated with Claude Code

@akashreddy-nr@claude
fix(translations): don't let machine translations overwrite human-tra…
0b46b75
…nslated locales Whether a page's locale goes to the human or the machine project is decided when it's queued, from the English page's `translate:` list. Nothing checked it again when the translation came back. A page that switched a locale to human translation after a machine job for it was sent, or while that job was stuck, still had the machine file written over the human one. For example, agentic-ai/mcp/overview.mdx got `translate: [jp]` on 2026-03-12, and a stuck machine job wrote English text over the human Japanese page in #26455 (#26487 then restored it). 52 English pages have had their `translate:` list added or changed in the last 12 months. When the machine job receives a file for a locale the English page lists under `translate:`, skip writing it and report it as done, so the record and job still complete and nothing retries it. Co-Authored-By: Claude Opus 5.5 <[email protected]>
@akashreddy-nr
akashreddy-nr requested a review from a team as a code ownerNovember 5, 2026 08:53
@github-actions

github-actionsBot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

Hi @akashreddy-nr 👋

Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days.

Please ensure the propsed changes look good by building it first in your local environment. Refer to this contribution guide to get the site up and running in your local.

If you really require a preview url, reach out to one of the writers and they will generate one for you.

@github-actionsgithub-actionsBot added the eng issues related to site functionality that requires engineering label Nov 5, 2026
@akashreddy-nr
akashreddy-nr merged commit fb70015 into developNov 5, 2026
18 checks passed
@akashreddy-nr
akashreddy-nr deleted the fix/translation-mt-skip-human-locales branch November 5, 2026 09:17
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Nandu-pnsNandu-pnsNandu-pns approved these changes

Assignees

No one assigned

Labels

engissues related to site functionality that requires engineering

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@akashreddy-nr@Nandu-pns