Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No Windows support? #3

Open
colinemondswieprecht opened this issue Feb 22, 2024 · 1 comment
Open

No Windows support? #3

colinemondswieprecht opened this issue Feb 22, 2024 · 1 comment

Comments

@colinemondswieprecht
Copy link

After installing the extension on Windows, I noticed that it does not appear to run correctly. For example, if I press Ctrl+Shift+P and run "Run supabase db reset command", nothing happens and this error appears in the Extension Host logs:

2024-02-22 10:18:41.459 [error] Error: ENOENT: no such file or directory, lstat '/c:/Users/colin.emonds/Code/foo'
	at lstatSync (node:fs:1670:3)
	at Object.lstatSync (node:electron/js2c/asar_bundle:2:4026)
	at executeCommand (c:\Users\colin.emonds\.vscode\extensions\anasaraid.vscode-supabase-cli-0.0.1\out\utils\exec-command.js:9:40)
	at c:\Users\colin.emonds\.vscode\extensions\anasaraid.vscode-supabase-cli-0.0.1\out\register.js:28:160
	at Generator.next (<anonymous>)
	at c:\Users\colin.emonds\.vscode\extensions\anasaraid.vscode-supabase-cli-0.0.1\out\register.js:8:71
	at new Promise (<anonymous>)
	at __awaiter (c:\Users\colin.emonds\.vscode\extensions\anasaraid.vscode-supabase-cli-0.0.1\out\register.js:4:12)
	at c:\Users\colin.emonds\.vscode\extensions\anasaraid.vscode-supabase-cli-0.0.1\out\register.js:28:72
	at s.h (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:150:175243)
	at s.$executeContributedCommand (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:150:176103)
	at d.S (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:147:5520)
        * snip many more lines *

The directory in the error message exists, but the path looks very odd. Is the leading slash intended?

@DuncanLHS
Copy link

Same issue here. Extension doesn't seem to connect to my DB properly and I get these error messages whenever I try running any command.

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

No branches or pull requests

2 participants