Closed michielbdejong closed 2 years ago
2022-11-01 14:35:25.142 INF ../../reva/pkg/storage/fs/nextcloud/nextcloud.go:213 > nc.do req https://nc1.docker/index.php/apps/sciencemesh/~einstein/api/storage/ListFolder {"ref":{"path":"/home"},"mdKeys":null} pid=7 pkg=rgrpc traceid=0e654ca3135e17116720f12aa54264a7 2022-11-01 14:35:25.383 INF ../../reva/pkg/storage/fs/nextcloud/nextcloud.go:232 > nc.do res https://nc1.docker/index.php/apps/sciencemesh/~einstein/api/storage/ListFolder {"error":"Folder not found"} pid=7 pkg=rgrpc traceid=0e654ca3135e17116720f12aa54264a7 2022-11-01 14:35:25.384 ERR ../../reva/internal/grpc/services/storageprovider/storageprovider.go:952 > error listing container: path:"/home" error="Unexpected response code from EFSS API: 404" pid=7 pkg=rgrpc traceid=0e654ca3135e17116720f12aa54264a7
Looks like my fix for https://github.com/pondersource/nc-sciencemesh/issues/225 broke this.
I think file paths in a Reva account should exist in a Home, and that's why /home
is sometimes (but not always) prepended.
Typing ls /
without hitting enter in reva-cli triggers a ListFolder /home
call.
If you then hit enter, a ListFolder /
call is sent.
Maybe the best approach is to map /var/www/html/data/einstein/files/
on Nextcloud to the /home
reva path and then just throw a meaningful error on attempts to access paths outside /home
.