fix(ci): unbreak bazel — netprobe zerolog dep + addon-sdk async-trait proc-macro (#3425) #3487
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!3487
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/ci-bazel-netprobe-zerolog-addonsdk-procmacro"
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?
Summary
Unbreaks
bazel test(invocation3893dbd3-bbda-4c31-8881-e2e53d298110). Two analysis/compile failures:1.
//go/pkg/agent/netprobe— unresolvedgithub.com/rs/zerologThe §2.2 apply-on-connect change (#3483) added a zerolog
Loggertonetprobe/sidecar.go, but thego_librarydeps weren't updated. Thego test ./...lane resolves it viago.mod; the bazel lane needs the explicit dep (this is the bazel-vs-go-test gap I'd flagged). → added@com_github_rs_zerolog//:zerolog.2.
//rust/addon-sdk:addon_sdk— proc-macro indepsasync-traitis a pure proc-macro; rules_rust requires it inproc_macro_deps, notdeps, or the target fails to analyze. → pulledasync-traitout of the sharedADDON_SDK_DEPSintoADDON_SDK_PROC_MACROS = crate_deps(["async-trait"])and setproc_macro_depson the library, therust_binary, and therust_test.Validation
bazel build //go/pkg/agent/netprobe:netprobe→ Build completed successfully (zerolog resolves + compiles).bazel build --nobuild //rust/addon-sdk:{addon_sdk, serviceradar-rust-sample-addon, addon_sdk_handshake_mtls_test}→ analyzes cleanly (the proc-macro error is gone).Note (separate, non-fatal)
The same invocation logs a web-ng SSR
bun builderror ("No matching export … for import 'Component'" for the 3 new dashboard components +RemoteAccessDesktopSession.test.jsx). That's caught in thephx.react.bun.bundlemix task (catch -> IO.inspect) so it doesn't fail the bazel tests — but it does mean the SSR bundle (priv/react/server.js) silently fails to build, breaking SSR rendering. Root cause:phx.react.bun.bundlerecursively globs every file underassets/component/srcand requires each toexport Component; the 3 dashboard files onlyexport default, and the co-located test isn't a component. I'll address that separately (add theComponentexport to the dashboard components; keep the test out of the SSR glob).🤖 Generated with Claude Code
lgtm