mirror of
https://github.com/koel/koel.git
synced 2026-04-26 17:25:59 +03:00
[GH-ISSUE #1102] Call to undefined method #647
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#647
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 @gorfreed on GitHub (Oct 9, 2019).
Original GitHub issue: https://github.com/koel/koel/issues/1102
This issue has been reported before, but there has never been any confirmed resolution for it, so I am creating another issue.
#1078
#1056
This occurs when trying to php artisan koel:sync. I tried all the steps suggested in the comments, which did not solve the issue, neither did composer update.
Apologies for not following the issue template. Its my 10th try or so in the past two years to get this thing running at all. Getting into the web-interface now was as far as i ever got, just to be stopped again by yet another bug. Considering the enormous list of open/unresolved issues, I just want to understand whether this software actually works reliably for anyone or if I should give up and save my. time.
@phanan commented on GitHub (Oct 9, 2019):
So you can't be bothered to follow a simple issue template but insist that a project's maintainers should spend their time to solve your problem? That's weird.
An issue template is there for a purpose. For instance, I can't reproduce the above problem at all in my environment (MacOS Mojave 10.14,
masterbranch, PHP 7.1.19). That's why I need as many details as possible to debug the issue (which you're hardly providing and as a result, not really helping).For your other statement/question:
@phanan commented on GitHub (Oct 9, 2019):
Closing in favor of #1078.