"Repeated File Operation and WebDAV Errors in Nextcloud 'Recognize' App"

[BoBBer446]

Which version of recognize are you using?

6.0.1

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?

28.0.1

Which Operating system do you have installed?

Ubuntu Server 22.04

Which database are you running Nextcloud on?

postgres:latest

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

24.0.7

How much RAM does your server have?

16

What processor Architecture does your CPU have?

x86_64

Describe the Bug

Multiple and repeated errors are occurring within the Nextcloud "Recognize" app during file operations and WebDAV processes. The errors include NotPermittedException during folder creation, BadRequest related to file size mismatches, and TypeError in PHP code, all pointing to possible issues with object definitions and network/storage interactions.

Expected Behavior

The app should perform file operations and WebDAV requests without any errors. All functionalities should work as intended, including file previews and metadata handling without throwing exceptions or causing server-side issues.

To Reproduce

Open the Nextcloud "Recognize" app.
Execute file operations such as uploading or moving files.
Observe the errors that occur during regular use, especially those related to file operations and WebDAV requests.
Consult the log files for specific error messages as detailed above.
Note: The exact reproduction steps may vary depending on how the app is used. The key point is that the errors listed are consistent and repeatable.

Debug log

version: '3.8'

services:
  nextcloud:
    image: nextcloud-custom-28:latest
    container_name: nextcloud
    hostname: nextcloud-server
    volumes:
      - /home/docker-projects/nextcloud:/var/www/html
    restart: always
    environment:
      - POSTGRES_HOST=postgres
      - POSTGRES_DB=nextcloud
      - POSTGRES_USER=nextcloud
      - POSTGRES_PASSWORD=securepassword
      - REDIS_HOST=redis
      - PHP_MEMORY_LIMIT=1024M
      - NEXTCLOUD_TRUSTED_DOMAINS=localhost
      - NEXTCLOUD_ADMIN_USER=mysuperusername-very-cool-next
      - NEXTCLOUD_ADMIN_PASSWORD=megasecure#_1
      - NEXTCLOUD_DEFAULT_PHONE_REGION=DE
    ports:
      - "8811:80"
    
    depends_on:
      - postgres
      - redis
  postgres:
    image: postgres:latest
    restart: always
    environment:
      - POSTGRES_DB=nextcloud
      - POSTGRES_USER=nextcloud
      - POSTGRES_PASSWORD=securepassword
    hostname: nextcloud-db
    container_name: nextcloud-db
    volumes:
      - /home/docker-projects/nextcloud/postgres:/var/lib/postgresql/data

  redis:
    image: redis:alpine
    restart: always
    hostname: nextcloud-redis
    container_name: nextcloud-redis

Dockerfile:

FROM nextcloud:28-apache

RUN apt-get update && \
    apt-get install -y libbz2-dev nano ffmpeg && \
    rm -rf /var/lib/apt/lists/*


RUN docker-php-ext-install bz2

[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 💙

[Ling128]

same issue

[marcelklehr]

Can you post the exact error log entries, please?

[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 💙

[github-actions]

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