[Bug]: `polyscope-server` fails with `exec format error`
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- macos
- Domain
- operating-systems, release
Research direction
Start with the installer at https://getpolyscope.com/install/server and the installed /Users/matthieu/.local/bin/polyscope-server on an ARM64 Mac. Check how the download selects and packages the server binary, then verify that the installed binary can execute polyscope-server login successfully on macOS ARM64.
Written by the indexing model from the issue text.
Description
Platform
macOS
Operating system version
macOS Tahoe latest, headless Mac Mini
System architecture
ARM64 (M1, M2, etc)
PolyScope Version
Latest
Bug description
I run this on a brand new Mac Mini:
curl -fsSL https://getpolyscope.com/install/server | bash
Downloading polyscope-server...
Installed polyscope-server to /Users/matthieu/.local/bin/polyscope-server
Next steps:
1. polyscope-server login # Authenticate with your Polyscope account
2. polyscope-server # Start the server
Tip: To keep polyscope-server running in the background, use a process
manager like supervisord or systemd. See our docs for details:
https://getpolyscope.com/docs/getting-started/standalone-server
Then:
polyscope-server login
zsh: exec format error: polyscope-server
- I checked that the file indeed exists (same result if I run it with the full path)
- the file is a binary (it is)
- tried re-installing just in case, same result
- I suspect it's installing the binary for the wrong CPU architecture? (per the error)
Note that I'm running the Polyscope Tauri app on the same machine without issues (I start it via a remote desktop), so I really think it's an issue with the binary file itself.
Steps to reproduce
No response
Relevant log output
- Dominant language
- No language data
- Stars
- 20
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from beyondcode/polyscope-community
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
beyondcode/polyscope-community#198 · 1 comment · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
All issues in beyondcode/polyscope-community
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
zephyrproject-rtos/zephyr#120011 ·
-
libc
Difficulty 2/5 1-2 days Newbie friendliness 76/100
llvm/llvm-project#225506 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
ValveSoftware/Proton#10167 ·
-
next-devel: s390x build fails — chccwdev/vmur/zkey missing from initramfs after s390utils 2.44 split Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
coreos/fedora-coreos-tracker#2228 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
pop-os/plymouth-theme#43 ·