Loic Nageleisen

Thanks Ivo, I'll look into these examples and attempt something.

@ioquatix yes I have. It works but it's quite annoying in the current state of GHA: - The runner process itself runs under Rosetta because at some point it hinges...

@ioquatix that's basically what I used (just follow the registering steps of macOS x64 provided by GHA's UI): ```yaml name: Build on: - push jobs: try-macos-arm64: name: Try macOS on...

@QuiiBz There's MacStadium as well: https://www.macstadium.com/configure?p=minig5&c=VGS2 Anyway even if there were M1 machines on AWS the cost is absolutely ludicrous. I don't see anyone using that unless they're heavily invested...

> Previously it was unspecified but now it's less ambiguous and I believe specifies a minimum time slice of 24hrs. (caveat: IANAL) There's a [lot of legal verbiage](https://www.apple.com/legal/sla/docs/macOSBigSur.pdf) (in Section...

@miketimofeev thanks for the info. To manage our expectations, would you be able to provide an order of magnitude (not even a ballpark), like are we talking about a week,...

As a workaround step I'm cross-compiling builds for `arm64` on `x86_64` runners for some projects by adding `-arch arm64` to `CFLAGS`, `CXXFLAGS`, and `LDFLAGS` (or its `cmake` equivalent `-DCMAKE_OSX_ARCHITECTURES=arm64`, see...

@ndbroadbent Sqreen Ruby agent engineer here. We tracked down this issue previously to conflicting unmangled libc++ symbols, and fixed it in libsqreen 0.3.0.0.3 (a native dependency of the Sqreen gem)....

I'm wondering if sassc is still alive somehow, last commit on master was 17 months ago, which is kind of concerning. Note: since this aimed for #192, there's a workaround...

> I guess that's not a guarantee though and might not always work? It's definitely not a guarantee enough, see [my comment over here](https://github.com/rubygems/rubygems/issues/3174#issuecomment-732320237). From experience maintaining a `mini_racer` fork...