Repository navigation
Conversation
Co-authored-by: arloor <admin@arloor.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Sets up the Cloud Agent development environment for
rust_http_proxyand records durable, non-obvious caveats for future agents inAGENTS.md.No application/source code was modified — only
AGENTS.mdgains a## Cursor Cloud specific instructionssection.Environment setup performed
stable(1.97.1) and set it as the default, because the crate isedition = "2024"(MSRV 1.85) but the base image shipsrustc1.83.autoconf autopoint flex bison gawk clang pkg-config make libelf-dev zlib1g-dev) so the optionalbpf*features build (--all-features).cargo fetch --locked(minimal, idempotent dependency refresh).Verification
cargo buildcargo fmt --all -- --checkcargo clippy -- -D warningscargo test./target/debug/rust_http_proxy -p 7788 --web-content-path ... --users .../metricsall workKnown pre-existing test failures
6 HTTP/2-upstream e2e tests fail with
hyper::Error(Io, BrokenPipe). Trace logs confirm the proxy actually returns200 OK; the failure is a race during HTTP/2 connection teardown. CI never runscargo test, so this is ungated and unrelated to environment setup. Documented inAGENTS.md.