nextcloud
"Checking CPU" never completes on FreeBSD
Describe the bug "Checking CPU" wheel just keeps spinning on FreeBSD
To Reproduce Steps to reproduce the behavior:
- Go to Recognize admin settings
- Watch the wheel spin round and round
Expected behavior It finishes detecting the CPU type and features
Recognize (please complete the following information):
- JS-only mode: [e.g. Yes/No]
- Enabled modes: [e.g. object detection, face recognition]
Server (please complete the following information):
- Nextcloud: 25.0.0
- OS: (FreeBSD Jail in) FreeBSD virtual machine (on Linux KVM Host)
- RAM: 16GiB
- Processor Architecture: amd64 (QEMU Virtual CPU version 2.5+)
Additional context Relevant error message:
Error: file_get_contents(/proc/cpuinfo): Failed to open stream: No such file or directory at /usr/local/www/nextcloud/apps/recognize/lib/Controller/AdminController.php#79
/proc/cpuinfo is a Linux thing and does not exist on FreeBSD. The serverinfo admin page of FreeBSD used to have the same problem, but now it works properly, you may want to check how they are determining CPU information now. But generally on FreeBSD you would use sysctl hw or sysctl hw.whatever.
But I would assume this is checking for AVX(2) anyway and pointless, since FreeBSD needs to use the JS implementation anyway.
Is it actually a blocking bug or something related to the administration panel only? Does the plugin works on TrueNAS/FreeBSD (in WASM mode)?
I'm getting this error as well, I think it's preventing the installation of Node which then fails on installing tensorflow, tried using wasm but got a permission error during the exec
Solved it by making a file /proc/cpuinfo with the content: "avx" At least it stopped the logs filling up with this bug. I think it wouldn't make a difference to have that content there as we have to use wasm mode
