Christoph Schmatzler

I am running into the same error, without any VPN connection. ``` ❯ colima version colima version 0.3.2 git commit: 272db4732b90390232ed9bdba955877f46a50552 runtime: docker arch: aarch64 client: v20.10.10 server: v20.10.11 ```

It's installed with `brew install velero`. Late 2021 M1 Pro MacBook Pro.

Updated the PR to do the same for SQLite and MySQL, should now also close #90.

Getting stuck here as well. The workaround from @unlocomqx allowed use of `setClient`, but now using `mutation` throws the same error.

This is solved in the new version by providing `os: aarch64`.

Is there a reason you used `dataloader-rs` over `async_graphql::dataloader`? I assume the latter didn't exist back when this repository was started, but their changelog doesn't go back far enough. Or...

I'm also aligned with `--warnings-as-errors`. It's the most common flag I've seen around.

Cursed patch for this: ``` diff --git a/Sources/TuistSupport/Utils/ColorizeSwift.swift b/Sources/TuistSupport/Utils/ColorizeSwift.swift index d9b9ac2d9..e0ab28fb8 100644 --- a/Sources/TuistSupport/Utils/ColorizeSwift.swift +++ b/Sources/TuistSupport/Utils/ColorizeSwift.swift @@ -108,5 +108,5 @@ extension String { private func applyStyle(_ codeStyle: TerminalStyleCode) -> String...

An alternative option might be to decouple Terminal styling from `String` and create an abstraction on top of it that acts as a builder. Something along the lines of `message.description.styled.cyan().bold().string()`...

That makes sense, I assumed there was a reason you initially vendored the file instead of using it as a dependency, so looked at it inside the repo. I'll file...