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

[BUG] Casino horses: multi-leg switcher labels R1/R2 do not follow header race number #8

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

Service / Project

casino (Node: pve01, LXC 19019)

Description

Cosmetic: when placing multi-leg bets, the leg switcher shows R1/R2/… independently of the current race number in the header. Example: header showed race 8 while switcher still showed R1/R2.

Steps to Reproduce

  1. Open horse racing mid-meeting (e.g. race 8)
  2. Select a multi-leg bet type (DBL / DT / TT / 6UP / ALUP)
  3. Open the leg switcher (關次)
  4. Compare labels to the header race badge

Expected Behavior

Switcher labels reflect absolute race numbers (or clearly map R1→current race N).

Actual Behavior

Switcher shows R1/R2 regardless of header race number (live: header 8, switcher R1/R2).

Error Logs / Evidence

  • Retest 05:31 live browser results (cosmetic)
  • src/modules/horses/horses-ui.js selectedLegs / leg switcher UI

Reported automatically by Grok QA Agent (Lumi).

### Service / Project **casino** (Node: `pve01`, LXC `19019`) ### Description Cosmetic: when placing multi-leg bets, the leg switcher shows R1/R2/… independently of the current race number in the header. Example: header showed race 8 while switcher still showed R1/R2. ### Steps to Reproduce 1. Open horse racing mid-meeting (e.g. race 8) 2. Select a multi-leg bet type (DBL / DT / TT / 6UP / ALUP) 3. Open the leg switcher (關次) 4. Compare labels to the header race badge ### Expected Behavior Switcher labels reflect absolute race numbers (or clearly map R1→current race N). ### Actual Behavior Switcher shows R1/R2 regardless of header race number (live: header 8, switcher R1/R2). ### Error Logs / Evidence - Retest 05:31 live browser results (cosmetic) - `src/modules/horses/horses-ui.js` selectedLegs / leg switcher UI --- *Reported automatically by **Grok QA Agent** (Lumi).*
admin added the
bug
qa/grok
pve01
 labels 2026-11-10 06:38:04 +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#8
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?