"Last Classification" date for Face Recognition not Updated (but Classification was Running Meanwhile)

[gohrner]

Which version of recognize are you using?

5.0.3

Enabled Modes

Object recognition, Face recognition, Video recognition, Music recognition

TensorFlow mode

Normal mode

Downstream App

Photos App

Which Nextcloud version do you have installed?

27.1.2

Which Operating system do you have installed?

Debian 12

Which database are you running Nextcloud on?

MariaDB 10.11.4

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

N/A

How much RAM does your server have?

4 GB

What processor Architecture does your CPU have?

x86_64

Describe the Bug

The "last classification" informatin in the Recognize web UI says that the last classification happened on 20th of Juli, 2023 (today we have 19th of Octobre, 2023), but I started a reclassification run only two weeks ago or so, and the number of files to be classified is (or was) slowly dropping, it started at about 11000 files. (Though I'm not sure if the number really changed much during the last few days.)

For object recognition it says that the last classification was 3 days ago, but no background jobs are planned.

Expected Behavior

The "last classification" date should show the most recent date on which regconize classified / analyzed a new file.

To Reproduce

I just enabled recognize again after disabling it for several month because previous version didn't properly respect the parallelization limits and tended to take down the whole server due by significantly overloading it.

Debug log

I can provide specific debug information if I know what I should add here. The whole debug log seems a bit risky due to potentially sensitive information - not sure if I would be able to reliably filter it out...

[github-actions[bot]]

Hello :wave:

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 :blue_heart:

[marcelklehr]

the number of files to be classified is (or was) slowly dropping

Did the number of clustered faces also increase? Since no clustering has happened yet and also no clustering jobs are scheduled I would conclude that indeed no face classification was done since july. You may check the the logs (perhaps set to debug first) for what's going on, feel free to post them here or send them to me via mail.

[gohrner]

@marcelklehr: But why did the counter drop from 11000 to the shown 7000-something (as stated above in the bug description) without any file being classified?

Maybe then I misunderstood what the counter is supposed to express? Doesn't it count as a "classification" if no face is detected in the image at all?

[marcelklehr]

why did the counter drop from 11000 to the shown 7000

Files can still be processed but if that fails the file is still removed from the queue without any result. That's why checking the log in this case is important.

[github-actions[bot]]

Hello :wave: 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 :blue_heart:

[github-actions[bot]]

This issue was closed because it has been stale for 5 days with no activity.