Skip to content

fix(server): skip non-UTF encoded filenames during migration. #3803

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 13, 2025

Conversation

deluan
Copy link
Member

@deluan deluan commented Mar 11, 2025

Fix #3787

Fix #3787

Signed-off-by: Deluan <deluan@navidrome.org>
@deluan deluan changed the title fix(server): skip non-UTF encoding during migration. fix(server): skip non-UTF encoded filenames during migration. Mar 11, 2025
@deluan deluan merged commit 5c0b6fb into master Mar 13, 2025
34 checks passed
@deluan deluan deleted the fix-migration-encoding branch March 13, 2025 11:10
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 12, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: Upgrade to 0.55.0 fails when file and path names are not encoded with UTF-8
1 participant