mirror of
https://github.com/EddieTheCubeHead/Stagnum.git
synced 2026-04-26 14:15:50 +03:00
[GH-ISSUE #411] [Bug]: Pool owner cannot skip if another user has promoted a song #232
Labels
No labels
bug
bug
client
design
documentation
feature
feature
infrastructure
pull-request
ready for development
server
server
spike
technical work
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Stagnum#232
Loading…
Add table
Add a link
Reference in a new issue
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?
Originally created by @EddieTheCubeHead on GitHub (Jul 5, 2024).
Original GitHub issue: https://github.com/EddieTheCubeHead/Stagnum/issues/411
Originally assigned to: @EddieTheCubeHead on GitHub.
Contact details
No response
Short description
If a pool has more than one users and a non-owner user promotes a song attempting to skip will raise "User had promoted a track that does not exist in pool" if it rolls for that other user.
Steps to reproduce
Expected behaviour
Skip works every time
Actual behaviour
If the skip would roll the song promoted by user 2, one of the error "User had promoted a track that does not exist in pool" is displayed
Additional information
If an easy fix for promoting other users' songs is not found it can be temporarily made illegal and fixed on a feature ticket.