mirror of
https://github.com/koel/koel.git
synced 2026-04-26 09:15:59 +03:00
[GH-ISSUE #534] [] operator not supported for strings #377
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#377
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 @3lpsy on GitHub (Feb 6, 2017).
Original GitHub issue: https://github.com/koel/koel/issues/534
I attempted to sync a few songs and received an "Unknown Error".
The song in question can be found here: http://freemusicarchive.org/search/?quicksearch=Ballad+for+typhon.
At first I thought it may be a filename error as the filename contained many "-" and "_" chracters, however, after changing the filename to "tester.mp3", I was still able to reproduce the error.
Koel Version: master branch.
OS: Mac (Sierra)
If such an error is to be expected on master branch, I'd recommend adding a failed sync feature where the sync function catches any exception, removes the songs entry (if added), and adds it to a failed_syncs table. I'd be more than happy to contribute to this functionality if it seems like something people would be interested in.
@phanan commented on GitHub (Feb 9, 2017):
This looks like a bug with getid3 and I don't think there's much Koel can do here.
Re:
failed_syncstable, how do we access it later? Personally I don't really think it's worth it.@nickster5001 commented on GitHub (Feb 12, 2017):
getid3 patched this issue on their end. You can get the new version from their github for now, until it gets including in a future koel release.
@3lpsy commented on GitHub (Feb 15, 2017):
Thanks for the input/solution. Went ahead and closed the issue.
@phanan When a sync fails with a given file, I think it would be beneficial to remove it from the sync directory, move the file to a failed directory, and store the original_path and the current_path to a failed_syncs table. Then if they wished to try again, they could trigger a "retry failed files" action which would run a sync on the failed directory.
However, depending on the current roadmap (is there public roadmap?), I don't know if this would be a high priority. Overall, I think adding file management to the front end would greatly improve the user experience.
@eplanet commented on GitHub (Feb 25, 2017):
I ran into the exact same issue and I think it should be reopened.
The
Unknown erroris too obscure: it is not acceptable that any underlying library could cause the whole import to fail, especially without even indicating which audio file is wrong.Hint for the impatient: Commenting lines that are supposed to set error messages do the trick. Even deleting
koel/vendor/james-heinrich/getid3/getid3/module.audio.mp3.phpseems to work fine for me…