William Boman

@reisnobre Yeah it's currently packaged in such a way that it requires JRE on the system. I remember seeing that they provide self-hosted JRE but decided to not use that...

Doing the following solved it for me: 1) ensure `GITHUB_PAT` is set to a valid GitHub API token (seems to only have been needed when running on GitHub's runners) 2)...

> Did you mean to leave a comment about solving a GitHub problem in an issue about a GitLab (not GitHub) API problem? Skip step 1 if not installing from...

What error message do you get?

Yeah I'd recommend submitting an issue upstream, as the error message even suggests. Maybe a temporary workaround could be to run the command twice in Mason should it fail the...

I've been wanting to tackle the management of runtimes/compilers more holistically, but I guess it wouldn't hurt adding a `node` package in the [core registry](https://github.com/mason-org/mason-registry), which would provide the `node`,...

> I ended up getting around this issue by having a bash script that pretends to be the runtime tool (e.g. npm) and execute the command inside a container (node:20...

@sv3ndk The pypi package won't be considered for addition to the core registry because: 1) it's not an official source 2) the way it's implemented is somewhat problematic imo. it's...

Hey! This is due to https://github.com/williamboman/mason.nvim/issues/152. Unfortunately all gem-based packages (three of them in total) are not functional yet with Mason. I've been reading up and experimenting with different solutions,...

Hey this should be fixed now. Let's reopen if you're still experiencing issues (you'll need to reinstall affected packages)