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

Mac M2 uses the wrong version of node for primsa to operate #1145

Open
MincePie opened this issue Aug 5, 2023 · 1 comment
Open

Mac M2 uses the wrong version of node for primsa to operate #1145

MincePie opened this issue Aug 5, 2023 · 1 comment
Labels
kind/bug A reported bug.

Comments

@MincePie
Copy link

MincePie commented Aug 5, 2023

Bug description

This thread sets out a problem that mac users are encountering with prisma: prisma/prisma#17869

I'm trying to solve it by replacing node /deleting node_modules, but I can't find the configuration required to let prisma run on mac.

I can see from the other thread that this is not a prisma issue, but any help figuring out what to do to find a way to use it on mac would be very much appreciated.

How to reproduce

Try using prisma commands in mac m2 with node

node -v  v18.17.0
node -e 'console.log(process.arch)' x64
arch i386

Expected behavior

trying to run prisma commands. they fail with this error message:

assertion failed [block != nullptr]: BasicBlock requested for unrecognized address
(BuilderBase.h:550 block_for_offset)
error Command failed with signal "SIGABRT".

Prisma information

prisma@5.1.1

Environment & setup

  • OS: Mac OS, Ventura
  • Database: MySQL

Prisma logs

No response

@MincePie MincePie added the kind/bug A reported bug. label Aug 5, 2023
@JClackett
Copy link

any ideas for a fix? still have this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A reported bug.
Projects
None yet
Development

No branches or pull requests

2 participants