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

[BUG] Casino horses: Six Up / All Up settle as losses on all-hit (array vs scalar legResults) #3

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

Service / Project

casino (Node: pve01, LXC 19019)
Public: https://casino.theforwardway.com

Description

Six Up (6UP) and All Up (ALUP) tickets settle as won=false / payout=0 even when every leg is a correct hit. The UI builds legResults as arrays (top-3 per leg), but the engine expects a scalar winner per leg for 6UP/ALUP. DBL/DT/TT correctly read array form.

Steps to Reproduce

  1. Open horse racing at https://casino.theforwardway.com
  2. Place an ALUP ticket with #1 in each of 2 legs (or 6UP with a pick in all 6 legs) using demo credit
  3. Wait for settlement / results panel
  4. Code path: horses-ui.js builds legResults = [pNums, generateSimulatedLegResults(12,3)×5]; engine HorseRacingEngine.js uses includes(winHorse) / includes(legResults[idx]) expecting scalars

Expected Behavior

An all-hit 6UP/ALUP ticket pays according to rules (scalar winner checks / carry-forward 滾存).

Actual Behavior

Live ALUP (#1×2 legs): race 2 result was 1-2-3-4 but the panel showed 未命中 for that leg. Engine probe: scalar-form PASS; array-form UI path FAIL (won=false, payout=0).

Error Logs / Evidence

  • Retest 05:31 §3 STILL OPEN + live browser § ALUP
  • src/modules/horses/horses-ui.js:778-785 (array legResults)
  • src/modules/horses/HorseRacingEngine.js:310 includes(winHorse), :326 includes(legResults[idx])
  • Fresh 15-type probe: 6UP/ALUP PASS* on scalar; FAIL on array-form UI results

Reported automatically by Grok QA Agent (Lumi).

### Service / Project **casino** (Node: `pve01`, LXC `19019`) Public: https://casino.theforwardway.com ### Description Six Up (6UP) and All Up (ALUP) tickets settle as `won=false` / payout=0 even when every leg is a correct hit. The UI builds `legResults` as arrays (top-3 per leg), but the engine expects a **scalar** winner per leg for 6UP/ALUP. DBL/DT/TT correctly read array form. ### Steps to Reproduce 1. Open horse racing at https://casino.theforwardway.com 2. Place an ALUP ticket with #1 in each of 2 legs (or 6UP with a pick in all 6 legs) using demo credit 3. Wait for settlement / results panel 4. Code path: `horses-ui.js` builds `legResults = [pNums, generateSimulatedLegResults(12,3)×5]`; engine `HorseRacingEngine.js` uses `includes(winHorse)` / `includes(legResults[idx])` expecting scalars ### Expected Behavior An all-hit 6UP/ALUP ticket pays according to rules (scalar winner checks / carry-forward 滾存). ### Actual Behavior Live ALUP (#1×2 legs): race 2 result was 1-2-3-4 but the panel showed 未命中 for that leg. Engine probe: scalar-form PASS; array-form UI path FAIL (won=false, payout=0). ### Error Logs / Evidence - Retest 05:31 §3 STILL OPEN + live browser § ALUP - `src/modules/horses/horses-ui.js:778-785` (array legResults) - `src/modules/horses/HorseRacingEngine.js:310` `includes(winHorse)`, `:326` `includes(legResults[idx])` - Fresh 15-type probe: 6UP/ALUP PASS* on scalar; FAIL on array-form UI results --- *Reported automatically by **Grok QA Agent** (Lumi).*
admin added the
bug
qa/grok
pve01
 labels 2026-11-10 06:37:57 +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#3
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?