KamoCRM

A 40001 wakati wa kuandaa taarifa kukamilika tena rolls saini nyuma

FixESigService
Shipped
8 Novemba 2026, 00:45 UTC
Author
Kamo
Commit
ae2e462

Magazeti ya kwanza ya Kumaliza kushindwa na 500 na kujaribu tena ilifanikiwa. Kukamilika taarifa walitunga ndani ya saini ya shughuli chini ya kukamata-wote: yao kusoma (mtumaji, template, nakala-kiungo tena-mint) hit YugabyteDB SQLState 40001 kulia baada ya safu ya saini walikuwa wameandikwa, repository alama ya kushiriki shughuli rollback-pekee, kukamata swallowed, na kushiriki kutupa UnexpectedRollbackException - rolling nyuma saini nzima. - EsignNoticeComposer (bean mpya): taarifa zote DB kazi, REQUIRES_NEW + @RetryOnDbConflict, tena-kusoma na id, kukimbia kutoka afterCommit. EsignNotificationService sasa tu inakamata ids, ratiba, na anatuma. Inatumika kwa kukamilika, decoderd, voided na kuisha taarifa. - Kuwasilisha () na decoder () ni @RetryOnDbConflict (kushirikiana-makumbusho mshauri, nje shughuli), hivyo yoyote 40001 ni alijaribu tena katika shughuli mpya. - kushindwa-laini flatten / cheti na matumizi ya rekodi sasa samaki rethrow a mgogoro wa muda mfupi au rollback-pekee hali (DbConflicts.rethrowIfDoomed) badala ya kumeza ni katika sumu kushiriki. - SigningSurvivesDbConflictTest inazalisha swallowed-kipekee rollback juu shughuli halisi proxies na inathibitisha taarifa na kuwasilisha kuishi 40001.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing