Investigate workaround for OSX Monterey & Bazel 4.2.x python env not found issue
- Dominant language
- C
- Stars
- 61
- Forks
- 26
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 11
Description
OSX Monterey removes python2 in default system path, and as a result, causing bazel 4.2.x iOS target build failure due to "python" not found error. Upgrading to bazel 5.x appears fixing the issue. However, this is dependent on gRPC c-core's bazel version upgrade
Investigate possible workaround with using bazel 4.2.1 on Mac OSX Monterey for iOS bazel tests.
related PR discussion https://github.com/grpc/grpc/pull/29599
----
cc @HannahShiSFB
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the iOS Bazel test build failure on macOS Monterey with Bazel 4.2.1, focusing on the reported missing "python" executable. Review the related gRPC pull request discussion for existing constraints. Done means a viable workaround is identified and verified for the affected iOS Bazel tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, macos
- Domain
- build-system, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100