Skip to content

bug: fix out of memory errors in continuous integration - #10

Merged
asymingt merged 9 commits into
mainfrom
asymingt/fix-oom-error
Nov 2, 2026
Merged

asymingt merged 9 commits into
mainfrom
asymingt/fix-oom-error

Conversation

@asymingt

@asymingt asymingt commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

The ros-central-registry has increased significantly in size. These are optimizations to ensure that the bazel server in continuous integration doesn't fall over due to an out of memory error.

asymingt and others added 9 commits November 2, 2026 18:36
Signed-off-by: Andrew Symington <simmers@google.com>
Signed-off-by: Andrew Symington <simmers@google.com>
Signed-off-by: Andrew Symington <simmers@google.com>
…#536)

(cherry picked from commit 182cdd3efef5aec383cb96c72428ef07e55237b2)
(cherry picked from commit ec2dd4d3c6ef456e68fe5f66b75ec9bc8e29c05e)
Default .bzl file pages to the documentation overview and render the
syntax-highlighted source below the module docstring and exported symbols.
Keep the explicit source route available.

(cherry picked from commit 7aeefeb24fc51ccfc1a515543b4a09a11a044186)
…ons type labels (#546)

Fixes #545

(cherry picked from commit 2a804d47bbdb769d1333c48f35b5aa3fb3366b18)
Partial pick of upstream bazel-contrib/bcr-frontend#534. Only the
--registry-source-url default applies to this fork:
registry-preview.bazel.build now returns 404, so the backup registry
used for repository-metadata fallback was never loading. The
--registry-url half of the upstream change is BCR-site-specific and is
already set for RCR in //:bcr.

(cherry picked from commit 73fac03655389a998237667c1aa8d909392f68be)
@asymingt
asymingt merged commit 4c28479 into main Nov 2, 2026
0 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants