nextcloud / nextcloud/recognize
`occ recognize:classify` : "Could not find file" using S3 as main storage
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 699
- Forks
- 68
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 5
Description
Which version of recognize are you using?
4.3.2
Enabled Modes
Face recognition
TensorFlow mode
WASM mode
Downstream App
other, please specify below
Which Nextcloud version do you have installed?
27.0.2
Which Operating system do you have installed?
Debian 11
Which database are you running Nextcloud on?
MariaDB
Which Docker container are you using to run Nextcloud? (if applicable)
N.A.
How much RAM does your server have?
4GiB
What processor Architecture does your CPU have?
ARM64
Describe the Bug
It seems that when using S3 as main storage, recognize can't access the files.
When using occ recognize:classify just after enabling face recognition, it spams Could not find file and removing 123456 from faces queue because it couldn't be found and only succeed to run on images hosted on my SFTP external storage, not on files hosted on S3 main storage.
I've ~600 photos.
It seems to work when using regular background job though, only occ recognize:classify seems to have this problem.
Expected Behavior
It should detect faces also on S3 main storage.
To Reproduce
- Setup a Nextcloud with S3 main storage
- Note : I use Hetzner CAX11 (ARM64) and Scaleway Object Storage.
- Add some photos
- (Add a SFTP external storage)
- Install Recognize
- Activate Face Recognition
- Run
occ recognize:classify - See that it succeeds only for images hosted on SFTP, not on S3
Debug log
https://paste.evolix.org/?e24017eeb4db4b87#9N4X5b5Sm1YM6n7t6gQmJDC1pe1Sku6K3etSQG51N1vR
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the occ recognize:classify entry point and the linked debug log, then compare its file access with the regular background job that succeeds. Reproduce the command against S3 main storage and SFTP external storage; done means classification can process images stored in S3 without Could not find file or removing queued items.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, cli, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100