mirror of
https://github.com/koel/koel.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #2019] [Bug]: playlist_user not created by setup #1065
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#1065
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 @basteyy on GitHub (Jul 12, 2025).
Original GitHub issue: https://github.com/koel/koel/issues/2019
Originally assigned to: @phanan on GitHub.
Read the Troubleshooting guide.
Reproduction steps
php artisan koel:init --no-assetsExpected behavior
All tables created correctly.
Actual behavior
Login failed, error message is shown:
Logs
Koel version
7.10.2
How did you install Koel?
Pre-compiled tar/zip archive
Additional information
@basteyy commented on GitHub (Jul 12, 2025):
All other tables created succesfully
@phanan commented on GitHub (Jul 12, 2025):
I don't know how other tables were created, but your database credentials were wrong, as clearly reported in the log.
@basteyy commented on GitHub (Jul 13, 2025):
The wrong credentials must pre setup attempts. All tables created by the setup routine. Actually I attached the log only, because it was required. When you look into the migrations, you won't find a corresponding for the missing table.
@phanan commented on GitHub (Jul 13, 2025):
There is, it's
2025_06_03_121538_modify_playlist-user_relationship.php:Without such table, there's no way the tests have been passing :)
@basteyy commented on GitHub (Jul 15, 2025):
I see. The table
playlist_collaboratorswas created by the setup successfully. The migration is marked as batched successfully. But obviously, the table was not renamed. I'm not familiar with Laravel and so I have no idea what's wrong with the migration. I can reproduce the failed renaming on different systems.Can you provide a current dump of the schema?
@phanan commented on GitHub (Jul 18, 2025):
Hey sorry for the late response. What if you rename the table manually?
Am Di., 15. Juli 2025 um 19:49 Uhr schrieb basteyy @.***
@basteyy commented on GitHub (Jul 21, 2025):
Renaming alone is not working. Schema is:
According to the error:
Just thinking that this problem is somehow connected to my config. I tried it again, and still the error. Have you tried to run the setup from scratch?
@phanan commented on GitHub (Jul 21, 2025):
Yes and the flow is covered in CI with every commit :)
It seems like your whole migration file (
2025_06_03_121538_modify_playlist-user_relationship.php) wasn't executed, and I'm not sure why. I would try to undo the renaming, remove the migration record from the migrations table, and runphp artisan migrateagain.Btw, is the DB version correct?
0.11.13-MariaDB-0ubuntu0.24.04.1-loglooks sus to me.@basteyy commented on GitHub (Jul 22, 2025):
I cut the
1at the beginning.This helps/fix it (btw, it was needed to perform
migrate:freshand create the first user again viaphp artisan koel:admin:change-password). So problem solved, but I still have the problem when drafting koel from scratch. I didn't test the docker container. But from source/pre-compiled, the same "error" still appears.