-
Notifications
You must be signed in to change notification settings - Fork 0
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
[P1] Paid-but-no-ticket, refunds, and seller payouts are incomplete
paymentsRazorpay, fulfillment, refunds, payoutsRazorpay, fulfillment, refunds, payoutspriority:p1Required before serious public onsalesRequired before serious public onsalesproductBooking rules, fairness, holds, trustBooking rules, fairness, holds, trustStatus: Open.#8 In akashcorex/tickity;[P1] 30-minute holds and weak bot limits let scalpers freeze an onsale
priority:p1Required before serious public onsalesRequired before serious public onsalesproductBooking rules, fairness, holds, trustBooking rules, fairness, holds, trustscaleConcurrency, throughput, 1L-user onsaleConcurrency, throughput, 1L-user onsaleStatus: Open.#7 In akashcorex/tickity;[P1] No virtual waiting room — 1L users are admitted straight into Convex
architectureBackend design, data model, isolationBackend design, data model, isolationpriority:p1Required before serious public onsalesRequired before serious public onsalesproductBooking rules, fairness, holds, trustBooking rules, fairness, holds, trustscaleConcurrency, throughput, 1L-user onsaleConcurrency, throughput, 1L-user onsaleStatus: Open.#6 In akashcorex/tickity;[P1] Queue position is O(n) per user and will melt under live subscriptions
architectureBackend design, data model, isolationBackend design, data model, isolationpriority:p1Required before serious public onsalesRequired before serious public onsalesscaleConcurrency, throughput, 1L-user onsaleConcurrency, throughput, 1L-user onsaleStatus: Open.#5 In akashcorex/tickity;[P0] joinWaitingList cannot survive a demand spike (OCC retry storm + O(n) inventory)
architectureBackend design, data model, isolationBackend design, data model, isolationpriority:p0Correctness bug or will fail a 1 lakh onsaleCorrectness bug or will fail a 1 lakh onsalescaleConcurrency, throughput, 1L-user onsaleConcurrency, throughput, 1L-user onsaleStatus: Open.#4 In akashcorex/tickity;[P0] Ticket issuance is client-side; Razorpay webhook does not exist
architectureBackend design, data model, isolationBackend design, data model, isolationbugSomething isn't workingSomething isn't workingpaymentsRazorpay, fulfillment, refunds, payoutsRazorpay, fulfillment, refunds, payoutspriority:p0Correctness bug or will fail a 1 lakh onsaleCorrectness bug or will fail a 1 lakh onsaleStatus: Open.#3 In akashcorex/tickity;[P0] Oversell: expired offer + successful payment still creates a ticket
architectureBackend design, data model, isolationBackend design, data model, isolationbugSomething isn't workingSomething isn't workingpaymentsRazorpay, fulfillment, refunds, payoutsRazorpay, fulfillment, refunds, payoutspriority:p0Correctness bug or will fail a 1 lakh onsaleCorrectness bug or will fail a 1 lakh onsaleStatus: Open.#2 In akashcorex/tickity;[Tracking] 1 lakh concurrent onsale: Tickity is not ready for Ticketmaster-scale demand
architectureBackend design, data model, isolationBackend design, data model, isolationpriority:p0Correctness bug or will fail a 1 lakh onsaleCorrectness bug or will fail a 1 lakh onsaleproductBooking rules, fairness, holds, trustBooking rules, fairness, holds, trustscaleConcurrency, throughput, 1L-user onsaleConcurrency, throughput, 1L-user onsaleStatus: Open.#1 In akashcorex/tickity;