-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Does not run on Intel mac #19
Comments
I have an Intel mac here as well (as well as an M1) one and can reproduce with 0.2.4. 0.2.3 still works for me. |
I found the issue, it turns out that CircleCI silently changed their runner to M1: |
I thought adding @lispyclouds perhaps you can take a look at this go stuff? |
I am glad that you were able to get something out of the not-very-informative bug report! |
At least you can still use 0.2.3 for now. Will take a look later. In can make a specific intel runner on circle to fix the problem for sure. |
I will take a closer look soon. |
Found the issue:
|
@lispyclouds Now none of the pods work anymore, I get:
I'll take a look... |
Interesting, I'm taking a look as well |
Alright, 0.2.7 finally works, tested both on mac intel and arm locally. |
Hi!
Thank you for this great interface for sqlite3!
I shared a babashka script using this pod to a user running an Intel mac, resulting in the following error:
I found #12, and suggested downgrading
0.1.0
, which worked perfectly. I think maybe the fix for M1 macs broke intel macs? I run an M1 mac myself, so it's hard for me to verify that the issue was introduced by #12, but it is so far my best guess!The text was updated successfully, but these errors were encountered: