SQL Error while running landmark recognition

[nielstron]

Which version of recognize are you using?

7.0.0

Enabled Modes

Object recognition, Face recognition

TensorFlow mode

Normal mode

Downstream App

Photos App

Which Nextcloud version do you have installed?

29.0.3

Which Operating system do you have installed?

Ubuntu 24.04 LTS

Which database are you running Nextcloud on?

mysql Ver 8.0.37-0ubuntu0.24.04.1 for Linux on x86_64 ((Ubuntu))

Which Docker container are you using to run Nextcloud? (if applicable)

No response

How much RAM does your server have?

8 GiB

What processor Architecture does your CPU have?

x86_64

Describe the Bug

Landmark recognition stopped, reporting that there is an error in the logs (see log)

Expected Behavior

No error during landmark recognition

To Reproduce

Not sure why this is happening.

Debug log

DriverException An exception occurred while executing a query: SQLSTATE[HY000]: General error: 1366 Incorrect string value: '\xE0' for column 'name' at row 1
Error while running background job OCA\Recognize\BackgroundJobs\ClassifyLandmarksJob (id: 1210, arguments: {"storageId":3,"rootId":264})

[github-actions]

Hello 👋

Thank you for taking the time to open this issue with recognize. I know it's frustrating when software
causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at
and if possible solved.
I try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it.
Until then, please be patient.
Note also that GitHub is a place where people meet to make software better together. Nobody here is under any obligation
to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can
collaborate to make this software better. For everyone.
Thus, if you can, you could also look at other issues to see whether you can help other people with your knowledge
and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and
try to fix the odd bug yourself. Everyone will be thankful for extra helping hands!
One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the forum,
to twitter or somewhere else. But this is a technical issue tracker, so please make sure to
focus on the tech and keep your opinions to yourself. (Also see our Code of Conduct. Really.)

I look forward to working with you on this issue
Cheers 💙

[marcelklehr]

It seems that a landmark was recognized that uses exotic Unicode characters in its name. do you have utf8_mb4 enabled in your db?

[github-actions]

Hello 👋
This issue is waiting for a response by the original poster for 2 weeks. We cannot keep track of whether individual issues
have resolved themselves or still require attention without user interaction. We're thus adding the stale label to this issue to schedule
it for getting closed in 5 days time. If you believe this issue is still valid and should be fixed, you can add a comment
or remove the label to avoid it getting closed.

Cheers 💙

[nielstron]

The error has since not reappeared, I did not do any changes to the database.