W
Wasp-langβ€’4mo ago
terrence

running wasp inside google idx error

I am trying to setup the dev environment test out opensaas with google online ide idx, but when I try to run command: wasp db migrate-dev wasp-bin: script: streamingProcess: exec: invalid argument (Bad file descriptor) Is this fixable? I think the IDX system is Nix, so maybe it's not compatible? I should avoid this online IDE in order to make it work? Thank you. 🐝 --- Compiling wasp project... -------------------------------------------------- [ Wasp ] Starting npm install [ Wasp ] [ Wasp ] removed 11 packages, and audited 833 packages in 4s ...... ...... βœ… --- Your wasp project has successfully compiled. ------------------------------- 🐝 --- Starting database migration... --------------------------------------------- wasp-bin: script: streamingProcess: exec: invalid argument (Bad file descriptor) @Wasp Team @Wasp Expert
8 Replies
miho
mihoβ€’4mo ago
Hmm how can we get access to IDX? 🀨 I don't have access to test it out unfortunately. Could share some details about the system like which OS it it and which version of Node.js is it running?
terrence
terrenceβ€’4mo ago
Node.js v20.11.1. and it uses nix to define packages etc uname -a Linux monospace-aiapp-1712068202823 6.1.75+ #1 SMP PREEMPT_DYNAMIC Fri Mar 1 15:14:26 UTC 2024 x86_64 GNU/Linux
MEE6
MEE6β€’4mo ago
Wohooo @terrence, you just became a Waspeteer level 1!
miho
mihoβ€’4mo ago
Maybe try running wasp clean then wasp start again πŸ˜„ Did you successfully work with Primsa on IDX before?
terrence
terrenceβ€’4mo ago
this is first time try IDX, in the begining it complains about no openssl, I added this package, it passed first round, then this error occured, stucked here... tried wasp clean, when I run wasp db migrate-dev, same error.
miho
mihoβ€’4mo ago
Since this error seems somehow related to Prisma, I'd maybe try a simple Prisma app to see what happens:
npx try-prisma@latest --template javascript/rest-express
cd javascript_rest-express
npx prisma migrate dev
npm run dev
npx try-prisma@latest --template javascript/rest-express
cd javascript_rest-express
npx prisma migrate dev
npm run dev
And then try to load the API at http://localhost:3000/users πŸ˜„ This is just trying to narrow down for which part IDX fails.
terrence
terrenceβ€’4mo ago
woking on this, will update you shortly
terrence
terrenceβ€’4mo ago
here is the api endpoint: https://3000-monospace-cuai-1712031728728.cluster-hf4yr35cmnbd4vhbxvfvc6cp5q.cloudworkstations.dev/users [{"id":1,"email":"alice@prisma.io","name":"Alice"},{"id":2,"email":"nilu@prisma.io","name":"Nilu"},{"id":3,"email":"mahmoud@prisma.io","name":"Mahmoud"}] everything seems works fine