-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Unknown system error -86 when spawning binary from @cubejs-backend/query-orchestrator (darwin-arm64) #8949
Labels
Comments
vieira
added a commit
to vieira/cube.js
that referenced
this issue
Nov 13, 2024
4 tasks
vieira
changed the title
Unknown system error -86 when spawning binary from @cubejs-backend/native (darwin-arm64)
Unknown system error -86 when spawning binary from @cubejs-backend/query-orchestrator (darwin-arm64)
Nov 13, 2024
ovr
added a commit
that referenced
this issue
Nov 13, 2024
@vieira, Could you give a try with the new release? Thanks |
@ovr Confirmed as fixed in 1.1.5. Thanks a lot! |
ptiurin
pushed a commit
to firebolt-db/cube
that referenced
this issue
Nov 27, 2024
cube-js#8950) Fixes: cube-js#8949 --------- Co-authored-by: Dmitry Patsura <zaets28rus@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When running cube-server I see some errors in the logs like:
During install I noticed there was a post install step that downloads a native binary.I have downloaded this file directly and after extracting it, trying to runindex.node
directly also produces an error.EDIT: This seems to be unrelated.
The cause seems to be the
cubestored
binary in@cubejs-backend/cubestore/downloaded/latest/bin
. On an Intel mac it runs fine but on ARM mac it fails to exec:The environment where I'm running is macOS 15.1 on M4 MBP:
To Reproduce
Steps to reproduce the behavior:
@cubejs-backend/server
on an ARM64 Mac (?)cubejs-server dev-server
query-orchestrator
errors in the logs spawning.Minimally reproducible Cube Schema
It doesn't seem to be exclusive to preAggregations but having a preAggregation triggers the error quickly and any query that would use the preAggregation fails. Some other queries still succeed.
Version:
1.1.3 (also tested with 1.0.5 and 1.1.4, same issue)
The text was updated successfully, but these errors were encountered: