chore(agent-data-plane): drop orphaned build-dependency - #2347
Conversation
agent-data-plane declares a build-dependency on chrono but has no build script. It had one until #291 moved build metadata capture into saluki-metadata and deleted it; the build-dependency was left behind. chrono stays a normal dependency, which is why cargo-machete never flagged this: it sees the crate used in the package and doesn't distinguish the section declaring it.
There was a problem hiding this comment.
More details
The removed chrono build-dependency is unreachable because agent-data-plane has no build script. Runtime chrono use remains backed by the normal dependency declaration, and build metadata is independently produced by saluki-metadata.
🤖 Datadog Autotest · Commit ab81497 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest
Binary Size Analysis (Agent Data Plane)Baseline: d6c6e40 · Comparison: ab81497 · diff ✅ Binary size difference within thresholdChanges by Module
Detailed Symbol Changes |
Regression Detector (Agent Data Plane)Run ID: Optimization Goals: ✅ No significant changes detectedFine details of change detection per experiment (5)Experiments configured
Bounds Checks: ✅ Passed (5)
ExplanationA change is flagged as a regression when |Δ mean %| > 5.00% in the regressing direction for its optimization goal AND SMP marks the experiment as a regression ( |
Summary
agent-data-planedeclares a[build-dependencies]entry forchronobut has no build script, so the dependency does nothing. It's a leftover: the crate did have abuild.rsuntil #291 moved build metadata capture intosaluki-metadataand deleted it, and the build-dependency was never cleaned up alongside it.Test plan
build.rsexists anywhere underbin/, and traced the history — added in [APR-107] chore: massively improve error messages #45, deleted in chore: add new crate,saluki-metadata, for easier cross-crate build metadata access #291cargo build --package agent-data-planesucceeds withCargo.lockunchanged, confirming nothing was resolving through the build-dependencymake check-unused-depsstill passes