GLM-5.3 للعمل الذي يسبق الإجابة

GLM-5.3 في التطبيق العملي

يراجع ⁦GLM-5.3⁩ إعادة محاولة الدفع: فترة احتمال التعطّل، والخصم الخارجي، ومفتاح ثابت لضمان عدم تكرار الأثر.

Review this Python payment handler: def pay(order): charge(order.card, order.total); db.mark_paid(order.id). A worker may retry after crashing between charge and mark_paid. Provide a concise failure timeline, a minimal idempotent design using a stable order key, and three executable-style regression cases. Do not claim a database transaction alone makes the external charge exactly-once.

Nothing ties the two steps together. charge is an external, non-transactional effect; the DB update is a separate operation. A crash (or worker timeout, or process kill, or deployment) between them leaves the order charged but unpaid — a retried worker charges again. Note: wrapping both lines in a DB transaction doesn't fix it. The charge is external; a rollback at t2 cannot "un-charge" the card, and retry still re-executes the charge. Exactly-once for an external effect requires idempotency, not atomicity. The key must be stable across attempts and derived from the order, never per-attempt or random, or both dedupe layers are useless.

سُجّلت هذه الإجابة من ⁦GLM-5.3⁩ في 29 أكتوبر 2026. مقتطفات مختارة من الإجابة الأصلية بالإنجليزية؛ حُذفت الأجزاء الأخرى. راجع التصاميم والشيفرة المُولّدة قبل استخدامها.