Closed
Bug 1774074
Opened 3 years ago
Closed 2 years ago
moz-phab self-update always fails with incorrect target path
Categories
(Conduit :: moz-phab, defect, P2)
Conduit
moz-phab
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: saschanaz, Assigned: sheehan)
References
(Regression)
Details
(Keywords: conduit-triaged)
Attachments
(1 file)
> moz-phab self-update
FileNotFoundError: [WinError 3] The system cannot find the path specified: 'C:\\Users\\sasch\\AppData\\Local\\Programs\\Python\\Python310\\Scripts\\moz-phab.exe\\moz-phab.exe' -> 'C:\\Users\\sasch\\AppData\\Local\\Programs\\Python\\Python310\\Scripts\\moz-phab.exe\\moz-phab-temp.exe'
Run moz-phab again with '--trace' to show debugging output
Sentry is attempting to send 2 pending error messages
Waiting up to 2 seconds
Press Ctrl-Break to quit
Windows seems to report the file path instead of the directory path here.
Updated•3 years ago
|
Severity: -- → S3
Keywords: conduit-triaged
Assignee | ||
Comment 1•2 years ago
|
||
Using sys.path[0]
to resolve the script directory works on
Linux/MacOS, however on Windows the full path to the starting
script is passed as `sys.path[0] instead of the directory to
the script.
Change how we define script_dir
to using sys.argv[0]
which
is the path to the script used to start Python. The parent
directory to this value is the script directory.
Updated•2 years ago
|
Assignee: nobody → sheehan
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•2 years ago
|
||
Should be fixed after 1.2.3 is released.
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 3•2 years ago
|
||
Just to clarify - the issue with the paths being incorrect will be fixed in the new version. However I'm doing some investigating and it seems the self-update mechanism has never worked on Windows in the past. I'm going to disable it for now in a new bug.
You need to log in
before you can comment on or make changes to this bug.
Description
•