Archimedes Trajano
Archimedes Trajano
Well at least one thing I can confirm that API call does NOT return any `realpath`
Anyway I think if the devs want to fix it, it may be as simple as changing the logic of https://github.com/nextcloud/photos/blob/295cb7fb1c308d03996475e64e5d7bcf810ebeea/src/mixins/FetchFacesMixin.ts#L120 and https://github.com/nextcloud/photos/blob/295cb7fb1c308d03996475e64e5d7bcf810ebeea/src/mixins/FetchFacesMixin.ts#L170C1-L176C52 To this when unminified, basically it doesn't...
> The issue has been fixed in NextCloud Server version 31.0.6 I'm on 31.0.6 and it doesn't recover from the error at least.
I set the path on the db as per https://github.com/nextcloud/photos/issues/3025#issuecomment-2917613697 and that worked out for me.
Or Immich :) but yeah Photos app is still buggy up until now. I can't find the part in the code myself to see what causes it. But my suspicion...
Looking into that train of thought it appears to be likely due to https://github.com/nextcloud/recognize/issues/1422
It appears that it is not pulling the trusted_proxies value from the config.php I get ``` The following trusted proxies are currently configured: "172.21.0.0/16" ``` But my trusted_proxies in config.php...
Actually I think this can be expanded a bit... each shell does the CDPATH differently. bash does it with `CDPATH` environment variable, `zsh` does it with `setopt auto_cd` followed by...
With `fish` it uses `set -gx cdpath ~/dev ~/projects ~/src`