mirror of
https://github.com/koel/koel.git
synced 2026-04-25 08:46:00 +03:00
[GH-ISSUE #1294] Infinite loop with console commands in non-interactive mode #744
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#744
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 @vitoyucepi on GitHub (Mar 26, 2021).
Original GitHub issue: https://github.com/koel/koel/issues/1294
Describe the bug
koel:initgoes into infinite loop if called in non-interactive mode when some required parameters not set.I checked only database related variables.
To reproduce
Steps to reproduce the behavior:
php artisan koel:init --no-interaction --no-assetson clear installExpected behavior
Fail with return non-zero return code.
Screenshots
Environment
Additional context
@phanan commented on GitHub (Mar 29, 2021):
What do you mean by "some required parameters not set"? What parameters are we looking at?
@vitoyucepi commented on GitHub (Mar 29, 2021):
Database related
@vitoyucepi commented on GitHub (Mar 29, 2021):
If I wouldn't set admin related variables
then installation will fail with error
@MichaIng commented on GitHub (Apr 11, 2021):
Since the
ADMIN_*settings have been removed withgithub.com/koel/koel@4432ad6c21, I don't think that the issue has to do with them. I initially as well made a wrong interpretation of ankoel:initcall failure, as it currently seems to error out on every database access one time, while repeating it reaches one step further: https://github.com/koel/koel/issues/1298#issuecomment-816872063Wile facing that the first time, I though the pre-defined media directory was the issue, and removing it from the .env and re-running
koel:initsucceeded. But actually the .env setting was not relevant, but repeatingkoel:initalone brought the success. Probably in your case it's the same.