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

Unsupported CPU architecture: x86_64 (linux-musl) #60

Open
azzamsa opened this issue Oct 20, 2023 · 2 comments
Open

Unsupported CPU architecture: x86_64 (linux-musl) #60

azzamsa opened this issue Oct 20, 2023 · 2 comments

Comments

@azzamsa
Copy link

azzamsa commented Oct 20, 2023

Hi.

The plugin fails in the ubuntu-22.04 CI but works locally.

jobs:
  code_quality:
    name: Code quality
    runs-on: ubuntu-22.04
    steps:
      - name: Checkout source code
        uses: actions/checkout@v4

      - uses: taiki-e/install-action@dprint

      - name: Show version information
        shell: bash
        run: |
          dprint --version

      - name: Ensure `fmt` has been run
        run:  dprint check
Run dprint --version
dprint 0.41.0
2s

Run dprint check
  dprint check
  shell: /usr/bin/bash -e {0}
Compiling https://plugins.dprint.dev/markdown-0.16.2.wasm
Compiling https://plugins.dprint.dev/toml-0.5.4.wasm
Error resolving plugin https://plugins.dprint.dev/prettier-0.27.0.json: Unsupported CPU architecture: x86_64 (linux-musl)
Error: Process completed with exit code 12.

But it works locally.

Fedora Linux 38 (Workstation Edition)

🙊 dprint --version
dprint 0.41.0
@scop
Copy link

scop commented Apr 13, 2024

A plugin compatible with the linux-musl dprint is important from the point that the musl dprint is commonly installed by things that need to work across different linux distros and versions. The prettier plugin cannot apparently currently be used in such setups.

@scop
Copy link

scop commented Oct 16, 2024

Projects that are dependent on prettier just for YAML formatting might be able to switch over to the g-plane/pretty_yaml plugin these days and sidestep this problem.

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

No branches or pull requests

2 participants