Skip to content

fix: bypass proxy for local server pubkey fetch in build script#2085

Draft
hulto wants to merge 1 commit intomainfrom
fix-cargo-build-tavern-reqwest-proxy-11601507693399375597
Draft

fix: bypass proxy for local server pubkey fetch in build script#2085
hulto wants to merge 1 commit intomainfrom
fix-cargo-build-tavern-reqwest-proxy-11601507693399375597

Conversation

@hulto
Copy link
Collaborator

@hulto hulto commented Mar 15, 2026

Fixes an issue where cargo build in implants/lib/pb fails to fetch the public key from the local Tavern server due to proxy misconfigurations in development environments.

Changes made:

  • Used reqwest::blocking::Client::builder().no_proxy().build().unwrap().get(&status_url).send() instead of reqwest::blocking::get(&status_url).
  • Replaced Display ({}) format for the error log with Debug ({:?}) to get more verbose error traces.

PR created automatically by Jules for task 11601507693399375597 started by @hulto

The `cargo build` command inside `implants/lib/pb` uses `reqwest` to fetch a public key from `http://127.0.0.1:8000/status`. In environments using proxies like Codespaces/devcontainers, `reqwest`'s default behavior failed to connect correctly.

Replaced `reqwest::blocking::get` with a `reqwest::blocking::Client::builder().no_proxy().build().unwrap().get()` initialization in `build.rs` to explicitly bypass any proxy configuration and directly connect to localhost.

Co-authored-by: hulto <7121375+hulto@users.noreply.github.com>
@google-labs-jules
Copy link
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@github-actions
Copy link
Contributor

Summary

Tests 📝 Passed ✅ Failed ❌ Skipped ⏭️ Other ❓ Flaky 🍂 Duration ⏱️
660    ±0 660    ±0 0    ±0 0    ±0 0    ±0 0    ±0 1ms    ±0

Previous Results

Build 🏗️ Result 🧪 Tests 📝 Passed ✅ Failed ❌ Skipped ⏭️ Other ❓ Flaky 🍂 Duration ⏱️
#1719 660 660 0 0 0 0 39.2s

Insights

Average Tests per Run Total Flaky Tests Total Failed Slowest Test (p95)
660 0 0 6.0s

Slowest Tests

Test 📝 Results 📊 Duration (avg) ⏱️ Duration (p95) ⏱️
TestDockerExecutor_Build_ContextCancellation 1 6.0s 6.0s
TestInteractiveShell 1 5.1s 5.1s
TestOtherStreamOutput 1 5.0s 5.0s
TestDockerExecutor_Build_SimpleEcho 1 4.0s 4.0s
TestDockerExecutor_Build_StreamsOutputInRealTime 1 2.9s 2.9s
TestDockerExecutor_Build_NonZeroExit 1 2.3s 2.3s
TestDockerExecutor_Build_MultiLineOutput 1 1.5s 1.5s
TestGetRandomName/NoDuplicates 1 1.4s 1.4s
TestGetRandomName 1 1.4s 1.4s
TestDockerExecutor_Build_StderrOutput 1 1.4s 1.4s

🎉 No failed tests in this run. | 🍂 No flaky tests in this run.

Github Test Reporter by CTRF 💚

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.

1 participant