Replies: 1 comment 2 replies
-
I locked the issue as the responses have simply been "Facing same issue", "👍 ", etc. It adds no value. There is absolutely no problem in recommending other packages (which is why your comment wasn't removed), it's a free world, people can use what they want. That being said, with over 20 users commenting and who knows however many it has affected, if no one with an M1 wants to debug and fix it, then it'll have to stay that way until one of the maintainers actually get an M1 to debug and fix. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
There's a well known bug on M1 processors:
#1541
I understand the point of the user that has closed the discussion, if no one with a M1 processor helps on this, no one can fix this.
But it's not a fault of the users that are using this library with M1 processor, so i can't understand why highlighting this bug should be marked as "off topic". Mark it as "known bug" and advise users that it will not be fixed (instead of leaving unanswered questions) should be the correct way to address this.
And suggesting an alternative package for users that unfortunately have a M1 processor and won't go to their company asking to throw away a bunch of mac and buy the previous mac models, would be appreciated.
Beta Was this translation helpful? Give feedback.
All reactions