You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: bottlecap/Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path bottlecap/Cargo.toml --workspace
Updating crates.io index
warning: spurious network error (3 tries remaining): [56] Failure when receiving data from the peer (CONNECT tunnel failed, response 403)
warning: spurious network error (2 tries remaining): [56] Failure when receiving data from the peer (CONNECT tunnel failed, response 403)
warning: spurious network error (1 try remaining): [56] Failure when receiving data from the peer (CONNECT tunnel failed, response 403)
Updating git repository `https://github.com/DataDog/saluki/`
error: failed to get `figment` as a dependency of package `bottlecap v0.1.0 (/tmp/renovate/repos/github/DataDog/datadog-lambda-extension/bottlecap)`
Caused by:
download of config.json failed
Caused by:
failed to download from `https://index.crates.io/config.json`
Caused by:
[56] Failure when receiving data from the peer (CONNECT tunnel failed, response 403)
Compilation error in src/flushing/service.rs:119:31: mismatched types for SketchPayload, found different version due to multiple versions in the dependency graph.
Bottlecap (Rust) | Clippy — 🔧 Needs a code fix, caused by this PR
CI on my pull request is failing. Help me find and fix the root cause of each failing job below — they were flagged as caused by changes in this PR, so focus on the diff. For each job, explain the failure and propose a fix.
Before you start, set up the Datadog software-delivery tooling so you can
query the CI data yourself:
1. Check whether you already have the Datadog software-delivery MCP tools
(e.g. a `search_datadog_ci_pipeline_events` tool) and the `unblock-pr` skill.
2. If either is missing, STOP and ask me for permission before installing
anything. Do not install or run anything until I have said yes.
3. Only with my explicit approval, set up the Datadog software-delivery MCP
server and skills by following:
https://docs.datadoghq.com/getting_started/software_delivery_mcp_tools/
then restart so the skill is picked up.
4. If I decline, skip all of the above and work from the context below alone.
Then run /unblock-pr — it will pull the CI data itself. The job context below is what we already know.
If /unblock-pr is not available — because I declined the setup above, or it did not install — work from the context below instead.
Datadog has already classified this failure as caused by changes in this PR.
Take that as given and work the fix:
1. Locate the change. Diff this branch against its base and find the change
that produces this error. Explain the mechanism, don't just name a file:
git fetch origin && git diff $(git merge-base origin/main HEAD)...HEAD
2. Reproduce it locally. Run the failing job's command or test before
proposing anything.
3. Propose the smallest fix that addresses the root cause — not a workaround,
not a broadened assertion, not a disabled or skipped test.
4. Re-run the same command to confirm, and say exactly what you ran.
5. If the failure turns out to be intermittent rather than deterministic, say
so plainly instead of "fixing" it — that is a flaky test, and patching it
hides the problem.
If the right move is to re-run the job rather than change code, use the job
link in the context below. For GitHub Actions: `gh run rerun <run-id> --failed`,
where the run ID is the number after `/runs/` in that URL (not the trailing
number, which is the job ID).
Branch: engraver-auto-version-upgrade/renovate/datadog-protos-digest
Bottlecap (Rust) | Build All
Commit: 19b205c1fb2457e2fc84888caef3e439fc024205
Error (code / build):
Mismatched types for `SketchPayload`. Found different versions in the dependency graph at src/flushing/service.rs:119 and src/flushing/service.rs:250.
CI job: https://github.com/DataDog/datadog-lambda-extension/actions/runs/33383758426/job/99461651319
Bottlecap (Rust) | Check
Commit: 19b205c1fb2457e2fc84888caef3e439fc024205
Error (code / build):
Compilation error in src/flushing/service.rs:119:31: mismatched types for `SketchPayload`, found different version due to multiple versions in the dependency graph.
CI job: https://github.com/DataDog/datadog-lambda-extension/actions/runs/33383758426/job/99461651346
Bottlecap (Rust) | Clippy
Commit: 19b205c1fb2457e2fc84888caef3e439fc024205
Error (code / build):
Compilation error in src/flushing/service.rs:119 due to mismatched types between expected and found `SketchPayload`.
CI job: https://github.com/DataDog/datadog-lambda-extension/actions/runs/33383758426/job/99461651347
Plus 1 more failing job not shown here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
f863626→cd6db96Warning
Some dependencies could not be looked up. Check the warning logs for more information.