Bug #8346
Find and fix any use cases with implicit use of working directory when accessing file-system resource
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
Related issues
History
#1 Updated by Hynek Cihlar 2 months ago
- Subject changed from Find and fix any use cases with implicit use of current directory when accessing file-system resource to Find and fix any use cases with implicit use of working directory when accessing file-system resource
File system access through the file system resource was exclusively executed on the client. Since #4065 it can also execute on the server.
With the move a potential issue arises. Use cases involving "implicit" working directory may break when the file system resource is executed on the server.
The goal of this issue is to identify those use cases and come up with a solution. There are several places in the FileSystemOps
and FileSystemDaemon
where the working directory is assumed. For example see the methods isPathRelativeToCurrentDir
, searchPath
, getWorkingDirectory
, setWorkingDirectory
, appendMissedPathEntry
.
This issue was identified in #8153-37.
#2 Updated by Hynek Cihlar 2 months ago
- Related to Feature #4065: server-side processing of client platform dependencies added