Skip to content

fix: anchor CLI socket under homedir instead of tmpdir - #64

Open
PriyeshPandey2000 wants to merge 1 commit into
diffusionstudio:mainfrom
PriyeshPandey2000:fix/cli-socket-tmpdir-mismatch
Open

fix: anchor CLI socket under homedir instead of tmpdir#64
PriyeshPandey2000 wants to merge 1 commit into
diffusionstudio:mainfrom
PriyeshPandey2000:fix/cli-socket-tmpdir-mismatch

Conversation

@PriyeshPandey2000

Copy link
Copy Markdown

Bug

dapi always reports "not running" even when the app is up: app (Finder/Dock launch) gets no $TMPDIR so os.tmpdir() falls back to /tmp, while dapi (terminal launch) inherits the shell's $TMPDIR (/var/folders/.../T). Each computed a different socket path, so dapi's connect always hit ENOENT.

Fix

Anchor the socket under ~/.diffusion-studio (mode 0700) instead of os.tmpdir(), so both processes agree on the same path regardless of launch context.

Closes #60

App (Finder/Dock launch) and dapi (terminal launch) get different
$TMPDIR values, so each computed a different socket path and dapi
could never connect. Anchor the socket under ~/.diffusion-studio
instead, which both processes agree on regardless of launch context.

Closes diffusionstudio#60
@vercel

vercel Bot commented Sep 11, 2026

Copy link
Copy Markdown

@PriyeshPandey2000 is attempting to deploy a commit to the Diffusion Studio Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CLI socket (diffusion-studio.sock) never created; every dapi command fails with 'not running' even though the app IS running and a project is open

1 participant