-
Notifications
You must be signed in to change notification settings - Fork 47
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
Processing loop #1133
Comments
Hello 👋 Thank you for taking the time to open this issue with recognize. I know it's frustrating when software I look forward to working with you on this issue |
Interestingly, of the recently added photos, these three are the only ones which are added to the landmark classification queue. Probably has something to do with it. The loop is as follows:
|
Huh, that's curious. And no errors? |
No, nothing. I also removed the causing files and re-uploaded them. Same issue |
Okay, to be fair, I did not re-upload the files, but move them on the filesystem and re-scanned the directories. That seems to have caused a problem. After actually uploading the files using the webinterface, it worked as supposed. I think, there might be a few factors playing a role here:
Just to provide information why I moved and re-scanned the file instead of just moving: This is still my workaround for #1118. Unfortunately, I cannot update, yet, as Group Folders is not yet compatible with NC 29. I'm hoping the fix for mentioned issue will make my workaround obsolete, so this should not happen anymore anyways. I'll test and post my findings here again when I have update NC and recognize to the latest version. |
Oh no, I was wrong. I moved another folder and again one file caused the loop issue, so I removed it and re-uploaded it via the webinterface. That did not help though, it's stuck in mentioned loop, even though it was uploaded "correctly". Again, it's a file which triggers landmark detection |
I did quite a bit of refactoring of the file hooks in v7 so, I'd rather hold off on digging into this deeper until you've updated to v7 / nc29 and can confirm that this is still happening. I hope that's ok. |
I think, it might be gone with v7. At least it did not happen for the last files I added. I guess we can close this. |
I was too quick in closing this issue. The files I tested did not trigger the landmark detection pipeline. It just happened again when I added some files which triggered the landmark detection. So the issue is unfortunately not fixed |
Is it possible that the files get re-inserted into the queue instead of them staying in there? Could you check the id column before and after imagenet classification? If the ids change then the files get reinserted |
Also, could it be that you or some other users have set up some flows in nextcloud flow that touch files based on tags? This could trigger the file listener and cause the files to get re-added to the queue. |
Sorry for the late response. With the recent images I added, I could no longer reproduce the issue. It seems a bit random, very odd. To your question before, I had checked that and the queue id's did not change. |
I'm just having the issue again today. Can confirm, the ids stay the same. Right now, I'm having a loop with 30 files. The following screenshot is taken during the imagenet classification. the 30 files stay in the imagenet queue and get added to the landmarks queue one by one. Well, procedure as described in the opening post |
After letting this loop run for ~1h, it suddenly managed to remove the files from the imagenet queue. Very weird. Could it have something to do with the use of redis? |
Seems like a race condition then 🤔 |
Which version of recognize are you using?
6.1.1
Enabled Modes
Object recognition, Face recognition
TensorFlow mode
Normal mode
Downstream App
Memories App
Which Nextcloud version do you have installed?
28.0.5
Which Operating system do you have installed?
Debian 12
Which database are you running Nextcloud on?
MariaDB
Which Docker container are you using to run Nextcloud? (if applicable)
No response
How much RAM does your server have?
32GB
What processor Architecture does your CPU have?
x86_64
Describe the Bug
I have three files which are processed by the object detector in a loop and not removed from the queue.
Expected Behavior
Files should be removed from the queue once processed
To Reproduce
Well, hard to say. Since this only occured for 3 of my >100k files, it's not clear to me what caused the issue
Debug log
The text was updated successfully, but these errors were encountered: