Patrick Balestra

I just ran into this issue, do you know if there's any official way of achieving this @intitni, or at least an idea of how complicated it would be to...

@acecilia In this specific case, Bazel is able to recover from the failure, while in #18696 it isn't, so I thought they might be different. It's possible that the culprit...

@coeuvre I sent you a gRPC log that I had from the second invocation that caused the build to fail. I hope it's useful. I can add some logging for...

I wonder, are you following the suggestion here to get Bazel to pick up correctly the change in Xcode versions? https://github.com/bazelbuild/rules_apple/blob/master/doc/common_info.md#xcode-version-selection-and-invalidation

Hello, unfortunately I don't have time to debug exactly what's wrong, but it must be one of the recently added contributions between the last two versions: https://github.com/MobileNativeFoundation/XCLogParser/compare/v0.2.36...v0.2.37 I have a...

Reverting in https://github.com/MobileNativeFoundation/XCLogParser/pull/199 and then will cut a new release. Thanks for reporting!

Have you tried the new flags suggested at the link to see if they work? If they do, then we welcome a contribution to change the wording and references to...

@jkmathew Most of the hardware information are being fetched in this class: https://github.com/spotify/XCMetrics/blob/c045eb9769e62a51bdf7d1d7bb7cbe0f2acb34dc/Sources/XCMetricsClient/Hardware%20Management/HardwareFactsFetcher.swift We use mostly standard commands to collect the hardware information, so you should be able to easily...

Very sorry about the delay here. Thanks for your change!

Hey @Arafo! I think this would be a great addition and we would welcome such a change. 👍