V34 — order_outbox jadvali

finalize-ep-10 yangiladi

Yangilandi: commit_sha, pr_url

qa-ep-10-t01-s03 statusni o'zgartirdi Review → Bajarildi

qa-ep-10-t01-s03 izoh qoldirdi

QA (mustaqil qayta tekshiruv, HEAD 1fb364e) — DONE. Test: OrderOutboxMigrationTest — 18 test, 0 failure, 0 error (Testcontainers PG16, toza HEAD, flock ostida bloklovchi run). MUTATSIYA TEKSHIRUVI (izolyatsiyalangan worktree /tmp/qa-EP-10-T01-S03 @1fb364e, 5 mutant — hammasi O LDI): (a) claim indeksi ustunlari (status,next_attempt_at) -> (object_type,object_id), NOM saqlangan => requiredClaimIndexExists YIQILDI (actual [object_type,object_id]). M3b topilmasi haqiqatda yopilgan: indexColumns() pg_index/pg_class/pg_attribute dan o qiydi, indeks NOMIGA tegmaydi. (b) dedup indeksidan UNIQUE olib tashlandi => 4 test yiqildi (dedupUniqueIndexIsPartialOnActiveStatuses, duplicateDedupKeyIsRejectedWhilePending + 2 ta ON CONFLICT testi). (c) dedup indeksining qisman WHERE i olib tashlandi (to liq UNIQUE) => 3 test yiqildi; jumladan AC3659 ning ikkinchi yarmi: onConflict...ThenAllowsAfterSent — "sent dan keyin yangi hodisa yozilishi kerak: Expecting actual not to be null". Ya ni 3659 ASOSLI, sinalgan. (d) claim indeksining qisman sharti pending -> processing => requiredClaimIndexExists YIQILDI (pg_get_expr predikati tekshiriladi). (e) chk_order_outbox_status da processing -> in_progress => 3 test yiqildi (validStatusesAreAccepted + 2 ta AbstractOutboxWorker testi). Har mutant target/classes dagi resursda kuchga kirgani grep bilan tasdiqlandi. FIXTURE XILMA-XILLIGI (QA linzasi): qotib qolgan qiymat YO Q — 6 xil event_type (order.recheck / order.received / order.delivery_failed / order.picking_started / order.delivered / order.created), 10+ xil object_id (900, 1024, 2024, 2025, 4242, 4343, 601-604, 777, 1..11). Ikkala terminal holat ALOHIDA sinalgan: ...ThenAllowsAfterSent (sent) va ...ThenAllowsAfterFailed (failed). sameOrderWithDifferentEventTypesDoesNotCollide bitta order_id (1024) ustida ikki xil event_type ni qamraydi. SPEC/KONTRAKT MOSLIGI: 06_orders.md §3 p.6 — outbox + @Scheduled worker, status/attempts/next_attempt_at, FOR UPDATE SKIP LOCKED, idempotentlik kaliti order_id+hodisa turi: mos. CHECK dagi 11 event_type (§10 dagi 10 notification + order.recheck) muzlatilgan openapi/v1/orders.yaml dagi nomlar bilan mos (order.received ~673, order.repriced ~726, order.delivering ~885, order.delivered ~939, order.delivery_failed ~999, order.cancelled ~1141). dedup_key oddiy varchar(150) — V28/V31 precedenti bilan bir xil, defekt emas. CROSS-CUTTING: tenant_id YO Q (AR-1) ✓; outbox naqshi AR-3/AR-12 ✓ (tashqi broker yo q); snake_case, timestamptz ✓; polimorf object_type/object_id da FK ataylab yo q — V28 precedenti ✓; parol/token log i yo q ✓. Worktree tozalandi (worktree remove --force), grep -rn MUTANT src/ bo sh, git status toza.

qa-ep-10-t01-s03 qabul mezonini belgiladi

✓ Worker indeksi (`status`, `next_attempt_at`) mavjud

qa-ep-10-t01-s03 qabul mezonini belgiladi

✓ Bir xil `event_type`+`order_id` uchun ikkinchi pending qator yozilmaydi (ON CONFLICT DO NOTHING), `failed`/`done` dan keyin esa YANGI qator yozish mumkin

coder-ep-10-t01-s03 yangiladi

Yangilandi: commit_sha

coder-ep-10-t01-s03 statusni o'zgartirdi Ishlanyapti → Review

coder-ep-10-t01-s03 fayllarni qayd etdi

1 ta fayl qayd etildi

coder-ep-10-t01-s03 qabul mezonini belgiladi

✓ Worker indeksi (`status`, `next_attempt_at`) mavjud

coder-ep-10-t01-s03 statusni o'zgartirdi Tayyor → Ishlanyapti

Agent ishni boshladi

coder-ep-10-t01-s03 ishga oldi

system statusni o'zgartirdi Ishlanyapti → Tayyor

Avtomatik bo'shatildi: 60 daqiqa signal yo'q

system bo'shatdi

Avtomatik bo'shatildi: 60 daqiqa signal yo'q

qa-ep-10-t01-s03 statusni o'zgartirdi Review → Ishlanyapti

qa-ep-10-t01-s03 izoh qoldirdi

QA (qa-EP-10-T01-S03) — QAYTARILDI. DDL (V34) TO'G'RI, kamchilik FAQAT testda. Baza: 18 test, 0 failure, 0 error (surefire XML dan o'zim tasdiqladim). === YIQILGAN MEZON: AC3660 === Mutatsiya M3b TIRIK QOLDI. Izolyatsiyalangan worktree'da indeks NOMINI o'zgarmagan holda ustunlarini almashtirilди: CREATE INDEX idx_order_outbox_status_next_attempt_at ON order_outbox (object_type, object_id) WHERE status = 'pending'; Jonli pg_indexes bilan tasdiqlandi — indeks endi (status, next_attempt_at) ni UMUMAN qamramaydi: ... USING btree (object_type, object_id) WHERE ((status)::text = 'pending'::text) Shunga qaramay 18/18 test YASHIL o'tdi. Ya'ni AC3660 ni hech narsa qo'riqlamayapti. SABAB — src/test/java/uz/erpbom/orders/OrderOutboxMigrationTest.java:333 assertThat(indexDef).contains("status").contains("next_attempt_at").contains("WHERE"); indexdef satri indeks NOMINI o'z ichiga oladi ('idx_order_outbox_status_next_attempt_at'), nom esa 'status' va 'next_attempt_at' pastki satrlarini allaqachon beradi. Assertion ustunlar ro'yxatini HECH QACHON o'qimaydi — nom bo'yicha yolg'on ijobiy. Kutilgan: ustun ro'yxati tekshirilsin. Olingan: faqat nom mos kelishi tekshirilgan. TUZATISH (test, DDL emas): indeksning ustun ro'yxatini nomdan AJRATIB tekshiring, mas. String cols = indexDef.substring(indexDef.indexOf("USING btree (")); assertThat(cols).contains("status").contains("next_attempt_at"); yoki aniqrog'i pg_index/pg_attribute orqali ustun nomlarini TARTIBI bilan o'qing: SELECT a.attname FROM pg_index i JOIN pg_attribute a ON a.attrelid=i.indrelid AND a.attnum=ANY(i.indkey) WHERE i.indexrelid='idx_order_outbox_status_next_attempt_at'::regclass ORDER BY array_position(i.indkey,a.attnum); va natija aynan [status, next_attempt_at] ekanini tasdiqlang. QABUL QILINISH SHARTI: yuqoridagi M3b mutanti (nom o'sha, ustunlar boshqa) testni YIQITISHI kerak. === SHU BILAN BIRGA (ikkinchi darajali, alohida yiqitmaydi) === OrderOutboxMigrationTest.java:347 da ayni naqsh: contains("dedup_key") — bu ham 'uq_order_outbox_dedup_key' NOMIDAN qanoatlanadi; contains("WHERE") predikat MAZMUNINI tekshirmaydi. AC3659 buni omon qoldirdi, chunki uni xatti-harakat testlari (ON CONFLICT) haqiqatan qo'riqlaydi — lekin 333-qator bilan birga tuzatilsa yaxshi. === O'TGAN MEZON: AC3659 ✅ === Jonli pg_indexes: CREATE UNIQUE INDEX uq_order_outbox_dedup_key ON public.order_outbox USING btree (dedup_key) WHERE ((status)::text = ANY ((ARRAY['pending','processing'])::text[])) — QISMAN UNIQUE, to'g'ri. Mutatsiyalar: M1 (WHERE olib tashlandi -> butun jadval UNIQUE) O'LDI — ikkala terminal holat testi ham ALOHIDA yiqildi (…AfterSent VA …AfterFailed) + dedupUniqueIndexIsPartialOnActiveStatuses. M2 (UNIQUE -> oddiy INDEX) O'LDI — 4 test. Ya'ni sent VA failed ikkalasi ham haqiqatan qoplangan. === TEKSHIRILGAN VA TO'G'RI (o'zgartirmang) === * Ustunlar V28/V31 bilan AYNAN bir xil 13 ta: id, event_type, object_type, object_id, dedup_key, payload, status, attempts, next_attempt_at, locked_at, last_error, sent_at, created_at. updated_at YO'Q, tenant_id YO'Q (AR-1). * locked_at BOR va nullable — AbstractOutboxWorker.claimBatch (status='processing' AND locked_at<=?) va markSent/markFailedAttempt (locked_at=NULL) bilan mos. M6 (locked_at o'chirildi) O'LDI — 3 test. * status CHECK = pending|processing|sent|failed; 'done' YO'Q (markSent 'sent' yozadi). M4 ('failed' olib tashlandi) O'LDI — 2 test. * event_type CHECK = 06_orders.md §10 dagi 10 ta hodisa + order.recheck (§3 p.6-b, R4) = 11. M5 (order.delivery_far_from_address olib tashlandi) O'LDI — allElevenOrderEventTypesAreAccepted. Har 11 qiymat alohida INSERT bilan sinaladi. * Fon ishi nomlash qarori migratsiya sarlavhasida hujjatlashtirilgan (31-58-qatorlar): (a) uchun alohida event YO'Q — order.received worker ishlov qismi (muzlatilgan kontrakt); (b) order.recheck. Qabul qilinadi. * MANZIL: order_outbox da manzil/koordinata/radius ustuni YO'Q — order.delivery_far_from_address faqat event_type nomi. To'g'ri (spec bo'shlig'i ochiq qoladi). * Fixture xilma-xilligi yetarli: object_id 1/501/601-604/777/802/900/1024/2024/2025/4242/4343, event_type turlicha; payload jsonb INSERT'dan keyin QAYTA O'QILIB solishtiriladi (payload->>'reason', ->>'delivery_attempts'::int). * Kontrakt fayllari commit'da o'zgarmagan (git show --stat 03f9bf9 = faqat 2 fayl). Mutatsiyalar izolyatsiyalangan git worktree'da (/tmp/qa-EP-10-T01-S03) o'tkazildi, worktree o'chirildi; asosiy daraxt toza, grep -rn MUTANT src/ bo'sh.

qa-ep-10-t01-s03 qabul mezonini belgiladi

✗ Worker indeksi (`status`, `next_attempt_at`) mavjud

qa-ep-10-t01-s03 qabul mezonini belgiladi

✓ Bir xil `event_type`+`order_id` uchun ikkinchi pending qator yozilmaydi (ON CONFLICT DO NOTHING), `failed`/`done` dan keyin esa YANGI qator yozish mumkin

coder-ep-10-t01-s03 statusni o'zgartirdi Ishlanyapti → Review

coder-ep-10-t01-s03 izoh qoldirdi

V34__order_outbox.sql: V28/V31 naqshi (AbstractOutboxWorker ustunlari), status pending|processing|sent|failed (AC/board matnidagi "done" emas — kod haqiqat manbai). event_type CHECK — 11 qiymat: §10 dagi 10 ta order.* notification hodisasi + order.recheck (07dan qayta tekshir, R4). §3 p.6-a (qoldiq tekshiruvi/avto set yig'ish/netting) uchun ALOHIDA event_type QO'SHILMADI: muzlatilgan kontrakt openapi/v1/orders.yaml (receive endpoint tavsifi, ~673-qator) buni ALLAQACHON hal qilgan — bitta order.received outbox qatori yoziladi, worker shu bitta qatorni qayta ishlaganda qoldiq tekshiruvi+avto set+netting ketma-ket bajaradi. object_type — faqat 'order' (bitta obyekt turi). dedup_key format {event_type}:{object_type}:{object_id}, UNIQUE qisman (WHERE status IN pending/processing). Mutatsiya tekshiruvi: izolyatsiyalangan worktree'da WHERE olib tashlandi -> 3 test qizil chiqdi (ikkala terminal holat - sent va failed - + indeks-shakl testi), keyin mutant tiklandi va grep MUTANT bo'sh tasdiqlangach commit qilindi. Test: 18/18 yashil (mvn -Dtest=OrderOutboxMigrationTest test).

coder-ep-10-t01-s03 yangiladi

Yangilandi: branch, commit_sha

coder-ep-10-t01-s03 qabul mezonini belgiladi

✓ Worker indeksi (`status`, `next_attempt_at`) mavjud

coder-ep-10-t01-s03 qabul mezonini belgiladi

✓ Bir xil `event_type`+`order_id` uchun ikkinchi pending qator yozilmaydi (ON CONFLICT DO NOTHING), `failed`/`done` dan keyin esa YANGI qator yozish mumkin

coder-ep-10-t01-s03 fayllarni qayd etdi

2 ta fayl qayd etildi

coder-ep-10-t01-s03 statusni o'zgartirdi Backlog → Ishlanyapti

Agent ishni boshladi

coder-ep-10-t01-s03 ishga oldi

pm-agent yaratdi

V34 — order_outbox jadvali