How would I update recognize to use a newer version of amphp/parallel?

💻 Development
1

I modified my image to use 8.4 and I noticed some deprecation messages on the logs. I checked parallel/lib/Worker/functions.php at 1.x · amphp/parallel · GitHub and it appears to have been corrected but the vendored version in recognize is still old.

Note it’d be my first time doing something like this with NextCloud.

2

I am sorry but could you elaborate a bit more details? What do you try to do? I looked the core dependencies and do not find the aforementioned dependencies.

Chris

3

I want to get rid of the warnings that appear when doing occ log:watch

  Error    PHP                OCA\Recognize\Vendor\voku\helper\UTF8::ucfirst(): Implicitly marking parameter $lang as nullable is deprecated,    2025-06-18T19:29:36-04:00
                              the explicit nullable type must be used instead at
                              /var/www/html/custom_apps/recognize/vendor/voku/portable-utf8/src/voku/helper/UTF8.php#10082

Usually it’s an easy patch of putting in a ? before the type name. I noticed that in the amphp code it already has it done but the currently released version of recognize uses an older version with the deprecated code.

I already patched mine locally by modifying the files in /var/www/html

4

Okay, so we are taking about the recognize app GitHub - nextcloud/recognize: 👁 👂 Smart media tagging for Nextcloud: recognizes faces, objects, landscapes, music genres. Sorry, I do not use it and neither do I know it.

In general, the dependency is defined in the composer file: recognize/composer.json at 1218d5488b53a7de008cf8cf48b2346898307939 · nextcloud/recognize · GitHub. the actual installation to the vendor directory happens during building the source code into an app tarball.

Chris

5

Hmm actually they never released the fix.

1.4.3 was their latest 1.4.x release and it didn’t have the code.

Seems someone raised the issue already Fix PHP 8.4 deprecations · amphp/parallel@94a6590 · GitHub

6

Until fixed upstream, it is hard to do something about the problem. you could fork and create a new package but this might be more than you want to invest. So, your next steps are more or less clear: get in touch with the maintainers and get this merged.

Chris

7

I think my logical next step is actually to abandon the effort of using NextCloud it’s just not polished enough to run a family cloud server especially with Photos and such.

It may be okay for simple file sharing, contact management and centralized backups though, but those would generally avoid the actual UI and use DAV or the VFS sync.

Now that I typed that out… maybe I just need something like a DAV server + VFS sync that doesn’t cost $$ like Mountain Duck