Flamenco: setup-assistant fails to accept Windows path as render storage location when running under WSL (Windows Subsystem for Linux) #102590

Closed
opened 2022-11-17 20:09:12 +01:00 by Greg Neumiller · 5 comments

Admittedly an edge case.

To reproduce:
Build flamenco via WSL (Windows Subsystem for Linux) Debian 10 under Windows 11 (path of least resistance for me)
Execute ./flamenco-manager -setup-assistant from within WSL
Use the link provided in the debug output to open the flamenco manager web page in your Windows browser
Click "Let's go" button on the Flamenco app page
Enter an existing path for shared storage (i.e: d:\blender-renders)

Result:

  1. The web app reports: "This path does not exist. Choose an existing directory."

  2. Debug msg from flamenco-manager: 'WRN shared storage path check failed cause="This path does not exist. Choose an existing directory." path="d:\blender-renders"'

Expected:

  1. Provide a more useful error message on the App's webpage
  2. Set a default path relative to flamenco-manager CWD and inform the user how to change it
    OR
  3. (Stretch) Convert the path as needed
Admittedly an edge case. To reproduce: Build flamenco via WSL (Windows Subsystem for Linux) Debian 10 under Windows 11 (path of least resistance for me) Execute ./flamenco-manager -setup-assistant from within WSL Use the link provided in the debug output to open the flamenco manager web page in your Windows browser Click "Let's go" button on the Flamenco app page Enter an existing path for shared storage (i.e: d:\blender-renders) Result: 1. The web app reports: "This path does not exist. Choose an existing directory." 2. Debug msg from flamenco-manager: 'WRN shared storage path check failed cause="This path does not exist. Choose an existing directory." path="d:\\blender-renders"' Expected: 1. Provide a more useful error message on the App's webpage 2. Set a default path relative to flamenco-manager CWD and inform the user how to change it __OR__ 3. (Stretch) Convert the path as needed
Sybren A. Stüvel was assigned by Greg Neumiller 2022-11-17 20:09:12 +01:00
Author

Added subscriber: @rlneumiller

Added subscriber: @rlneumiller

Changed status from 'Needs Triage' to: 'Archived'

Changed status from 'Needs Triage' to: 'Archived'

Build flamenco via WSL (Windows Subsystem for Linux) Debian 10 under Windows 11 (path of least resistance for me)

What does that path of least resistance lead to? I mean, you can just download Flamenco for Windows and run it directly, you don't need to build it yourself.

The described issue is not an issue with Flamenco. A Linux build won't understand a Windows path, even when you run it on WSL. If you really want to run Flamenco Manager on WSL, you have to treat it as a Linux program.

> Build flamenco via WSL (Windows Subsystem for Linux) Debian 10 under Windows 11 (path of least resistance for me) What does that path of least resistance lead to? I mean, you can just download Flamenco for Windows and run it directly, you don't need to build it yourself. The described issue is not an issue with Flamenco. A Linux build won't understand a Windows path, even when you run it on WSL. If you really want to run Flamenco Manager on WSL, you have to treat it as a Linux program.
Sybren A. Stüvel changed title from Windows: Flamenco Setup Assistant: Shaman: setup-assistant fails to accept Windows path as render storage location when running under WSL (Windows Subsystem for Linux) to Flamenco: setup-assistant fails to accept Windows path as render storage location when running under WSL (Windows Subsystem for Linux) 2022-11-21 17:54:48 +01:00
Author

Path of least resistance == building any version on my Windows machine in preparation for debugging\contributing bug fixes, etc. ( I did not have msys2\mingw64 set up yet).
A linux build of flamenco does not currently understand a Windows path (but it could). As I mentioned above, this is an edge case, but if I tried it I suspect that someone else will and now they don't need to bother filing a bug.

Path of least resistance == building any version on my Windows machine in preparation for debugging\contributing bug fixes, etc. ( I did not have msys2\mingw64 set up yet). A linux build of flamenco does not currently understand a Windows path (but it could). As I mentioned above, this is an edge case, but if I tried it I suspect that someone else will and now they don't need to bother filing a bug.

In #102590#1449461, @rlneumiller wrote:
Path of least resistance == building any version on my Windows machine in preparation for debugging\contributing bug fixes, etc. ( I did not have msys2\mingw64 set up yet).

That's a good goal, thanks :) D16562: Fix #102633 by having Windows-specific commands in Makefile helps already, so I want to land that ASAP.

A linux build of flamenco does not currently understand a Windows path (but it could).

I think #100195 (Allow finishing setup assistant without Blender on Manager) would be a better start. That way you could just not have Blender directly available for the Manager, and only supply a path that's used by the Workers. Ideally we'd even have a system where a Worker could do a quick test whether Blender is actually available (and with which version) at that path and report that back to the Manager (for display in the worker details, for example). But I digress.

As I mentioned above, this is an edge case, but if I tried it I suspect that someone else will and now they don't need to bother filing a bug.

👌

> In #102590#1449461, @rlneumiller wrote: > Path of least resistance == building any version on my Windows machine in preparation for debugging\contributing bug fixes, etc. ( I did not have msys2\mingw64 set up yet). That's a good goal, thanks :) [D16562: Fix #102633 by having Windows-specific commands in Makefile](https://archive.blender.org/developer/D16562) helps already, so I want to land that ASAP. > A linux build of flamenco does not currently understand a Windows path (but it could). I think #100195 (Allow finishing setup assistant without Blender on Manager) would be a better start. That way you could just not have Blender directly available for the Manager, and only supply a path that's used by the Workers. Ideally we'd even have a system where a Worker could do a quick test whether Blender is actually available (and with which version) at that path and report that back to the Manager (for display in the worker details, for example). But I digress. > As I mentioned above, this is an edge case, but if I tried it I suspect that someone else will and now they don't need to bother filing a bug. :ok_hand:
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: studio/flamenco#102590
No description provided.