2004 chorebazel fix rbe docker image #2472
No reviewers
Labels
No labels
1week
2weeks
Failed compliance check
IP cameras
NATS
Possible security concern
Review effort 1/5
Review effort 2/5
Review effort 3/5
Review effort 4/5
Review effort 5/5
UI
aardvark
accessibility
amd64
api
arm64
auth
back-end
bgp
blog
bug
build
checkers
ci-cd
cleanup
cnpg
codex
core
dependencies
device-management
documentation
duplicate
dusk
ebpf
enhancement
eta 1d
eta 1hr
eta 3d
eta 3hr
feature
fieldsurvey
github_actions
go
good first issue
help wanted
invalid
javascript
k8s
log-collector
mapper
mtr
needs-triage
netflow
network-sweep
observability
oracle
otel
plug-in
proton
python
question
reddit
redhat
research
rperf
rperf-checker
rust
sdk
security
serviceradar-agent
serviceradar-agent-gateway
serviceradar-web
serviceradar-web-ng
siem
snmp
sysmon
topology
ubiquiti
wasm
wontfix
zen-engine
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
carverauto/serviceradar!2472
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refs/pull/2472/head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Imported from GitHub pull request.
Original GitHub pull request: #2007
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2007
Original created: 2025-11-24T17:06:43Z
Original updated: 2025-12-08T06:54:37Z
Original head: carverauto/serviceradar:2004-chorebazel-fix-rbe-docker-image
Original base: main
Original merged: 2025-11-24T18:41:21Z by @mfreeman451
User description
IMPORTANT: Please sign the Developer Certificate of Origin
Thank you for your contribution to ServiceRadar. Please note, when contributing, the developer must include
a DCO sign-off statement indicating the DCO acceptance in one commit message. Here
is an example DCO Signed-off-by line in a commit message:
Describe your changes
Issue ticket number and link
Code checklist before requesting a review
PR Type
Enhancement, Bug fix
Description
Update RBE executor Docker image from v1.0.14/v1.0.15 to v1.0.16
Add bison, flex, gperf to RBE and ARC runner Dockerfiles
Remove source-based build toolchain for bison/flex/gperf
Simplify PostgreSQL extension build by using pre-installed tools
Update ARC runner image digest and NATS version to 2.12.2
Diagram Walkthrough
File Walkthrough
6 files
Update RBE executor Docker image versionUpdate container image and add ARC runnerUpdate RBE platform container image versionsUpdate RBE platform container image versionUpdate execution config container image versionUpdate ARC runner image digest reference3 files
Add bison, flex, gperf build toolsAdd gperf to ARC runner dependenciesUpdate NATS server version to 2.12.21 files
Update ARC runner base image reference2 files
Update ARC runner image digest referenceUpdate RBE image build documentation version3 files
Remove bison source tree build targetRemove flex source tree build targetRemove gperf source tree build targetImported GitHub PR comment.
Original author: @qodo-code-review[bot]
Original URL: https://github.com/carverauto/serviceradar/pull/2007#issuecomment-3571836769
Original created: 2025-11-24T17:07:12Z
PR Compliance Guide 🔍
Below is a summary of compliance checks for this PR:
Unpinned toolchain versions
Description: The build step relies on host/executor PATH tools (flex, bison, gperf) without pinning
versions, which can lead to non-reproducible builds and potential supply chain risk if the
executor image changes unexpectedly.
BUILD.bazel [1578-1583]
Referred Code
🎫 #2004
during builds.
build steps.
compatible versions in the runtime PATH.
toolchains.
Codebase context is not defined
Follow the guide to enable codebase context checks.
Generic: Comprehensive Audit Trails
Objective: To create a detailed and reliable record of critical system actions for security analysis
and compliance.
Status: Passed
Generic: Meaningful Naming and Self-Documenting Code
Objective: Ensure all identifiers clearly express their purpose and intent, making code
self-documenting
Status: Passed
Generic: Secure Error Handling
Objective: To prevent the leakage of sensitive system information through error messages while
providing sufficient detail for internal debugging.
Status: Passed
Generic: Secure Logging Practices
Objective: To ensure logs are useful for debugging and auditing without exposing sensitive
information like PII, PHI, or cardholder data.
Status: Passed
Generic: Security-First Input Validation and Data Handling
Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent
vulnerabilities
Status: Passed
Generic: Robust Error Handling and Edge Case Management
Objective: Ensure comprehensive error handling that provides meaningful context and graceful
degradation
Status:
Build tool checks: The new genrule relies on host-provided tools (flex/bison/gperf) and only checks their
presence, which may still fail at runtime if versions are incompatible or PATH/PKG_CONFIG
paths are insufficient, lacking fallback handling.
Referred Code
Compliance status legend
🟢 - Fully Compliant🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label
Imported GitHub PR comment.
Original author: @qodo-code-review[bot]
Original URL: https://github.com/carverauto/serviceradar/pull/2007#issuecomment-3571841324
Original created: 2025-11-24T17:08:11Z
PR Code Suggestions ✨
No code suggestions found for the PR.