You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Command to reproduce & Last.FM username:/streak & BotiasTurbo
Describe the bug:
A couple days ago, I saved a streak on a song for 5miinust
Since then, I didn't save new streaks
Today, I saved another streak for the same song, album and artist
While streakhistory still shows both separate streaks, the initial message from issuing /streak showed that my saved streak would have been updated, even though it was the first time I used the command on this specific streak.
Screenshots:
Version (use.fmstatus):
Not listed
The text was updated successfully, but these errors were encountered:
I double checked, and it isn't possible for the bot to reply with 'Streak has been updated' unless there was already a streak in the database. Could it be that maybe the wrong streak was updated?
What I think might have happened is LastFM had a hiccup for a handful of days and caught itself after a little while, which lead to me continuing the streak from the other day.
However, the starting date of the saved streak fits the issue occurrence and report date:
Command to reproduce & Last.FM username:
/streak
& BotiasTurboDescribe the bug:
A couple days ago, I saved a streak on a song for 5miinust
Since then, I didn't save new streaks
Today, I saved another streak for the same song, album and artist
While streakhistory still shows both separate streaks, the initial message from issuing
/streak
showed that my saved streak would have been updated, even though it was the first time I used the command on this specific streak.Screenshots:
Version (use
.fmstatus
):Not listed
The text was updated successfully, but these errors were encountered: