Weekly GitHub Report for Xla: November 10, 2025 - November 17, 2025 (12:01:42)
Weekly GitHub Report for Xla
Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.
Table of Contents
I. News
1.1 Recent Version Releases:
No recent version releases were found.
1.2 Version Information:
Please provide the version release information you would like me to analyze and summarize.
II. Issues
2.1 Top 5 Active Issues:
We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.
As of our latest update, there are no active issues with ongoing comments this week.
2.2 Top 5 Stale Issues:
We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.
- New
nvshmemrule breaks the build: This issue reports a build failure caused by a newnvshmemrule introduced in a recent update, which leads to an error related to therepository_ctxobject lacking agetenvmethod during the CUDA configuration step. The reporter is seeking guidance on whether they need to make changes on their side to resolve the problem or if the fix must come from the open_xla project, along with an estimated timeline for addressing the issue. - Failed to Parse MLIR generated by Torchax: This issue describes a problem encountered when exporting a PyTorch model to MLIR using the torch-xla torchax export API, where the generated MLIR fails to parse due to an unregistered operation 'vhlo.rsqrt_v2' in the 'vhlo' dialect. The user is attempting to compile the exported MLIR into an XLA binary using XLA AOT compilation but faces deserialization errors with StableHLO_v1.9.5, despite using compatible versions of torch, torchxla, and building XLA from the corresponding commit.
- support bazel modules: This issue is about inquiring whether there are plans to adopt Bazel modules within the project, as Bazel modules have seen significant adoption. The user points out that XLA is currently the only package in their Bazel build that does not support Bazel modules, highlighting a potential gap in compatibility.
- Gpu collective performance model bug: This issue concerns a bug in the gpu_collective_performance model where an update to the lowLatencyBandwidth for AMD links was made without corresponding changes to the CUDA section. As a result, invoking the gpu_collective_performance model with H100 settings leads to a failure, indicating incomplete or inconsistent updates in the performance model code.
- Cross compile to ARM with custom gcc: This issue concerns difficulties encountered when attempting to cross-compile the XLA project from an x86 architecture to ARM64 using a custom GCC compiler. The user reports that despite using the
--config=cross_compile_linux_arm64flag in the Bazel build system, the build process persistently tries to produce an x86 binary, indicating a possible misconfiguration or missing step in the cross-compilation setup.
2.3 Open Issues
This section lists, groups, and then summarizes issues that were created within the last week in the repository.
Issues Opened This Week: 0
Summarized Issues:
As of our latest update, there are no open issues for the project this week.
2.4 Closed Issues
This section lists, groups, and then summarizes issues that were closed within the last week in the repository. This section also links the associated pull requests if applicable.
Issues Closed This Week: 0
Summarized Issues:
As of our latest update, there were no issues closed in the project this week.
2.5 Issue Discussion Insights
This section will analyze the tone and sentiment of discussions within this project's open and closed issues that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.
As of our last update, there are no open or closed issues with discussions going on within the past week.
III. Pull Requests
3.1 Open Pull Requests
This section provides a summary of pull requests that were opened in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.
Pull Requests Opened This Week: 0
As of our latest update, there are no open pull requests for the project this week.
3.2 Closed Pull Requests
This section provides a summary of pull requests that were closed in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.
Pull Requests Closed This Week: 0
As of our latest update, there are no closed pull requests for the project this week.
3.3 Pull Request Discussion Insights
This section will analyze the tone and sentiment of discussions within this project's open and closed pull requests that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.
As of our last update, there are no open or closed pull requests with discussions going on within the past week.
IV. Contributors
4.1 Contributors
Active Contributors:
We consider an active contributor in this project to be any contributor who has made at least 1 commit, opened at least 1 issue, created at least 1 pull request, or made more than 2 comments in the last month.
If there are more than 10 active contributors, the list is truncated to the top 10 based on contribution metrics for better clarity.
| Contributor | Commits | Pull Requests | Issues | Comments |
|---|---|---|---|---|
| alekstheod | 46 | 10 | 0 | 2 |
| rao-ashish | 2 | 1 | 0 | 17 |
| emilyfertig | 0 | 0 | 0 | 12 |
| shawnwang18 | 8 | 3 | 0 | 0 |
| mingxu1067 | 6 | 2 | 0 | 3 |
| Tixxx | 2 | 2 | 0 | 4 |
| sergachev | 5 | 1 | 0 | 2 |
| mtsokol | 5 | 3 | 0 | 0 |
| mmakevic-amd | 7 | 0 | 0 | 0 |
| olegshyshkov | 0 | 0 | 0 | 7 |