nextcloud / nextcloud/recognize

Recognize doesn't seem to be processing group/shared folders

Open
#1,492 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug waiting for more information
Dominant language
PHP
Stars
699
Forks
68
Avg merge
1d 4h
Merged PRs (30d)
5

Description

Which version of recognize are you using?

11.01

Enabled Modes

Object recognition, Face recognition, Video recognition

TensorFlow mode

GPU mode

Downstream App

Files App

Which Nextcloud version do you have installed?

33.01

Which Operating system do you have installed?

Truenas

Which database are you running Nextcloud on?

postgres

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

Truenas stock

How much RAM does your server have?

64 GiB

What processor Architecture does your CPU have?

x86_64

Describe the Bug

After going through a full walk. I've noticed that certain folders seem to be completely omitted from photos. They also have no tags nor are there any faces recognized in them. IE. Group folders, where folders are shared with more than one user, are never processed and therefore never get their tags added or faces processed.

Expected Behavior

Group folders should also get processed in a way where the user can index and search people or tags.

To Reproduce

install group folder plugin. Create a group folder. put a photo in group folder. Attempt re-crawl. File in group folder is not processed.. Or at least it doesn't show up for the user as processed.

Debug log

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the report with the Group folders plugin: create a group folder, add a photo, and run a re-crawl. Trace why the photo is omitted from processing, then verify that tags and recognized faces are available to the user after indexing. No debug log or source file is identified in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, postgres, tensorflow
Domain
backend, machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.