edgedb
Windows: [error] this action cannot be run on win32
Output of EdgeDB Language Client:
2024-09-13 21:21:03.704 [info] Extension activated.
2024-09-13 21:21:03.704 [error] this action cannot be run on win32
I assume you are using Windows? To be honest the language server was not tested on Windows yet.
I looks like I'll have to get a windows machine :sweat:
This seems to be a wider spread issue across multiple implementations of the gel-cli wrappers. Using gel purely from the command line in Windows works fine, but the same calls made from wrapped contexts like npx or this plugin result in the same "this action cannot be run on win32" error.
@nerdoza There are likely two issues here -- the first is that the gel language server doesn't currently support windows, though I believe we can offer at least syntax highlighting as a backup.
As for the npx issue, I believe this is just missing Windows support in gel-js here (@scotttrinh, can we add support for platform == windows?):
https://github.com/geldata/gel-js/blob/7681512862a5bec545c47b6cd1ca7a9608e78d81/packages/gel/src/cli.mts#L304
@mmastrac, I agree on both points, but this does seem to be something specific to the rename since the same commands worked when using the edgedb alias running exactly the same code. The DX on Windows before the rename was fine and all commands were proxied through to the WSL runner without issue, it's only been since the rename that these issues have started popping up so I suspect it's a simple aliasing issue that hasn't been identified yet.
I've tried fresh installs of the gel server to see if it was just a evolutions issue but that didn't resolve the issue. I'm currently having to rebuild all our code bases as full container runtimes to get around the issues since our development has ground to a halt since the rename. We've even decided to drop it from all greenfield projects until we can get a reliable DX experience again.
@nerdoza was the language server functional on Windows? I wasn't sure if we ever supported it and it looks like perhaps we started showing errors where we might have been silently ignoring them before.
We don't want to break your Windows development workflow for sure. I'm not sure how this got broken as we believed it was all working as expected, but please feel free to file issues with whatever information you can provide. We will certainly try to fix any regressions.
No, we currently don't support language server on windows. I'm not sure if we even build binaries for it.