Set up Cursor Cloud dev environment#219
Draft
123liuziming wants to merge 1 commit into
Draft
Conversation
Co-authored-by: Liu Ziming <123liuziming@users.noreply.github.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
3 participants
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 development environment for this OpenTelemetry Python Contrib / LoongSuite instrumentation monorepo and documents it for future Cursor Cloud agents. No product code is changed.
AGENTS.mdwith a## Cursor Cloud specific instructionssection describing theuv+toxworkflow, common commands, required system build libs, and non-obvious gotchas.Environment setup performed
uvand system build libs (build-essential pkg-config libpq-dev default-libmysqlclient-dev librdkafka-dev libsnappy-dev python3-dev) needed to compile native deps (psycopg2, mysqlclient, etc.).uv syncbuilds the dev virtualenv at.venv/(all workspace packages +tox/tox-uv/pre-commit).uvif missing, thenuv sync.Verification
.venv/bin/tox -e ruff.venv/bin/tox -e py312-test-instrumentation-requests.venv/bin/tox -c tox-loongsuite.ini -e py312-test-loongsuite-instrumentation-langchain-latestRequestsInstrumentor+ConsoleSpanExporterGET example.comhttp.status_code: 200Hello-world span output
hello_world_span.log
Gotcha discovered
The
opentelemetry-instrumentauto-instrumentation CLI currently fails in theuv syncvenv (core API/SDK pinned to upstreammainis ahead of the bundled logging instrumentor:LogRecord.__init__() got an unexpected keyword argument 'context'). Per-packagetoxenvs are unaffected (they pinCORE_REPO_SHA). Use programmatic instrumentation for quick smoke tests. Documented inAGENTS.md.To show artifacts inline, enable in settings.