admin/patproject
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases Wiki Activity

[BUG] Casino horses: betting window only 20s; UI is slow so bets land at 00:00–00:03 #6

New Issue
Open
opened 2026-11-10 06:38:01 +08:00 by admin · 0 comments
admin commented 2026-11-10 06:38:01 +08:00
Owner
Copy Link

Service / Project

casino (Node: pve01, LXC 19019)

Description

raceCountdown is still 20 seconds. With multi-leg / multi-combination selection, the UI is slow enough that legitimate bets often submit at 00:00–00:03 on the countdown (accepted, but race against the clock). Blocks reliable live coverage of all 15 HKJC types in one window.

Steps to Reproduce

  1. Open horse racing
  2. Select a multi-combination or multi-leg bet (e.g. QTT 24 combos, ALUP, 6UP)
  3. Attempt to confirm before countdown hits 0
  4. Observe countdown at submit often 00:00–00:03

Expected Behavior

Enough time (or pre-betting) to place complex tickets before the race locks.

Actual Behavior

20s window unchanged (horses-ui.js:25 init, :887 reset). Live run 05:35–05:48: several bets accepted at 00:00–00:03.

Error Logs / Evidence

  • Retest 05:31 §3 STILL OPEN + live browser note
  • src/modules/horses/horses-ui.js:25, :887 raceCountdown=20
  • Related feature request: pre-betting during results popup / longer window

Reported automatically by Grok QA Agent (Lumi).

### Service / Project **casino** (Node: `pve01`, LXC `19019`) ### Description `raceCountdown` is still 20 seconds. With multi-leg / multi-combination selection, the UI is slow enough that legitimate bets often submit at 00:00–00:03 on the countdown (accepted, but race against the clock). Blocks reliable live coverage of all 15 HKJC types in one window. ### Steps to Reproduce 1. Open horse racing 2. Select a multi-combination or multi-leg bet (e.g. QTT 24 combos, ALUP, 6UP) 3. Attempt to confirm before countdown hits 0 4. Observe countdown at submit often 00:00–00:03 ### Expected Behavior Enough time (or pre-betting) to place complex tickets before the race locks. ### Actual Behavior 20s window unchanged (`horses-ui.js:25` init, `:887` reset). Live run 05:35–05:48: several bets accepted at 00:00–00:03. ### Error Logs / Evidence - Retest 05:31 §3 STILL OPEN + live browser note - `src/modules/horses/horses-ui.js:25`, `:887` `raceCountdown=20` - Related feature request: pre-betting during results popup / longer window --- *Reported automatically by **Grok QA Agent** (Lumi).*
admin added the
bug
qa/grok
pve01
 labels 2026-11-10 06:38:01 +08:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
agent/antigravity
Assigned to Antigravity developer agent
bug
Something isn't working
feature
New feature or implementation request
pve01
Host node pve01
pve02
Host node pve02
pve03
Host node pve03
pve04
Host node pve04
qa/gemini
Reported or tested by Gemini QA agent
qa/grok
Reported or tested by Grok QA agent
status/in-progress
Actively being coded or debugged
status/resolved
Completed and verified in production
status/testing
Ready for QA agents (Gemini/Grok) to verify
No Label
bug
pve01
qa/grok
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: admin/patproject#6
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?