Spaces:
Running
Dev mode status breaks my space everytime
I will be using a fully functional space, then I tr to enable devmode, which causes it to get stuck like this everytime. I'm able to connect ssh through CLI, but it doesn't seem to register it. Upon trying with VS code online, it errors with workspace not found, and through local it says: "Failed to connect to the remote extension host server (Error: EISDIR: illegal operation on a directory, read)" If I click on the button attached to the error, I can view these 3 codes: notificationsAlerts.ts:42 Failed to connect to the remote extension host server (Error: EISDIR: illegal operation on a directory, read)
c @ notificationsAlerts.ts:42
8console.ts:137 [Extension Host] Failed to load message bundle for file c:\Users\brand.vscode\extensions\ms-edgedevtools.vscode-edge-devtools-2.1.5\out\extension
w @ console.ts:137
console.ts:137 [Extension Host] Error: EISDIR: illegal operation on a directory, read
w @ console.ts:137
Hello
@tomboyman
!
There are some requirements that must be met for the Dev Mode to work properly for Docker Spaces.
You can find the list of requirements here: https://huggingface.co/dev-mode-explorers#docker-spaces
Can you please make sure your Space satisfies all those conditions?
Hi
@tomboyman
, you haven't answered the last comment so I'll consider this issue as resolved and close this issue.
Feel free to re-open it if you're still having problems or questions with this!
Cheers