i think chmod issues

[hype]

thanks for presentation at ZeroSpace :

current setup :
OS: Ubuntu 25.04 x86_64
Kernel: Linux 6.14.0-36-generic
Shell: bash 5.2.37
CPU: Intel(R) Core(TM) i7-8700K (12) @ 4.70 GHz
GPU 1: NVIDIA GeForce RTX 4090 [Discrete]
Memory: 2.33 GiB / 61.64 GiB (4%)
Disk (/): 489.36 GiB / 1.79 TiB (27%) - ext4

I tried getting this working both ways... CLI works fine... but when I installed the custom_node... I was kinda hoping the custom_node would see what I had created via the CLI ? but no they dont talk to each other ? is that correct ?

and then when I tried JUST the custom_node path I think there might be a chmod issue ? because if I create the workspace path and I uncheck existing models and I see the the progress bar push to 100%... im now on the create or import screen... but if I run an ls -al on ~ it never creates ~/comfygit... if I click the "x" and click "comfygit" in the header bar... im back at the workspace path and existing models card again. and for fun if I do this all again and even say create new environment "001_TEST" and uncheck switch to this new env. it again is pretending to create everything... and now I see swith to existing env "001_TEST" it hangs on 60% "starting new environment" because I dont think it even actually exists.

any ideas ?

[hype]

The mock API is enabled by default unless VITE_USE_MOCK_API=false is set.

I then rebuilt the frontend... but I could never get the custom_node to actual play nice... it finally got past the first welcome screen after I changed VITE_USE_MOCK_API - I could create new ENV but could never actually jump between them

again the CLI works fine... but being able to control everything from the custom_node would be nice.

[akatz-ai]

Hi @hype (Joshua)! Thanks so much for trying/debugging the repo! The last couple days have been a whirlwind of travel for me so apologies for the delay.

I think mock API is a skill issue on my part, I was doing some testing on my macbook before the event and likely pushed a build with VITE_USE_MOCK_API enabled by default. Will get that resolved asap.

The CLI and 'Manager' (custom node) both use the 'core' library from the monorepo, so in theory they should be acting on the machine in the same way. Ideally if you created a workspace via the cli like 'cg init' and it creates the default workspace at ~/comfygit/, then if you started up a ComfyUI install with the node installed and tried to create/switch environments it should find the existing ~/comfygit on your filesystem instead of prompting you to create a new one. But you're right there's probably a permissions issue or other bug causing the environments to fail at create time.

The handoff process could also use an update to improve error handling in cases where the target environment is missing.

I've got my own ubuntu machine with similar specs set up locally so I'll give it a test run and report back if I encounter the same issue.

[akatz-ai]

Hi @hype, I went ahead and released patch #12 which should fix the 'Mock' by default bug. The code was incorrectly set up to enable mocking by default if there was no .env in the environment explicitly disabling it. I tested on my own linux setup to double check the patch works properly.

I believe the issues you were seeing was due to the mock API never calling the backend, so the results you were seeing in the UI was all fake data.

If you pull the latest custom node version from github or the manager (v0.0.11) the code should now correctly recognize your existing workspace set up by the CLI tool. Let me know if you're still seeing issues!

P.S. If you're switching between environments and it seems 'stuck' at 60%, you can check the true progress of the handoff sequence by running 'cg orch logs' in a new terminal to get a log dump of what the orchestrator is doing behind the scenes. If you see something that looks like an error it may have died in the process, otherwise it's just downloading pytorch which always takes a while 😅. And if the orchestrator seems stuck or has stale data, you can also run 'cg orch kill' followed by 'cg orch clean' to stop any running orchestrator process and clean up any stale files.

[hype]

thank you. sorted and working.