Skip to content

Set up Cursor Cloud dev environment#219

Draft
123liuziming wants to merge 1 commit into
mainfrom
cursor/setup-dev-environment-4a61
Draft

Set up Cursor Cloud dev environment#219
123liuziming wants to merge 1 commit into
mainfrom
cursor/setup-dev-environment-4a61

Conversation

@123liuziming

Copy link
Copy Markdown
Collaborator

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.

  • Adds AGENTS.md with a ## Cursor Cloud specific instructions section describing the uv + tox workflow, common commands, required system build libs, and non-obvious gotchas.

Environment setup performed

  • Installed uv and 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 sync builds the dev virtualenv at .venv/ (all workspace packages + tox/tox-uv/pre-commit).
  • Update script (run on VM startup): installs uv if missing, then uv sync.

Verification

Check Command Result
Lint .venv/bin/tox -e ruff ✅ ruff/format/uv-lock/rstcheck passed
Tests (upstream) .venv/bin/tox -e py312-test-instrumentation-requests ✅ 80 passed
Tests (LoongSuite) .venv/bin/tox -c tox-loongsuite.ini -e py312-test-loongsuite-instrumentation-langchain-latest ✅ 150 passed
Hello-world Programmatic RequestsInstrumentor + ConsoleSpanExporter GET example.com ✅ CLIENT span emitted, http.status_code: 200

Hello-world span output

hello_world_span.log

Gotcha discovered

The opentelemetry-instrument auto-instrumentation CLI currently fails in the uv sync venv (core API/SDK pinned to upstream main is ahead of the bundled logging instrumentor: LogRecord.__init__() got an unexpected keyword argument 'context'). Per-package tox envs are unaffected (they pin CORE_REPO_SHA). Use programmatic instrumentation for quick smoke tests. Documented in AGENTS.md.

To show artifacts inline, enable in settings.

Open in Web Open in Cursor 

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@github-actions

Copy link
Copy Markdown

This PR has been automatically marked as stale because it has not had any activity for 14 days. It will be closed if no further activity occurs within 14 days of this comment.
If you're still working on this, please add a comment or push new commits.

@github-actions github-actions Bot added the Stale label Jun 30, 2026
@ralf0131

Copy link
Copy Markdown
Collaborator

📋 CLA Reminder

Thank you for this PR! Before it can be merged, please sign the Contributor License Agreement (CLA).

👉 Sign the CLA here

Once signed, the CLA status will update automatically and we can proceed with approval.


Automated notification by github-manager-bot

@ralf0131 ralf0131 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary

This PR adds an AGENTS.md file with Cursor Cloud dev environment instructions for the LoongSuite Python monorepo — toolchain overview, common commands, and non-obvious gotchas.

The documentation is well-structured and accurate based on the repo setup. No code issues found.

Notes

  • ⚠️ CLA is not signed yet — this PR cannot be approved/merged until the contributor signs the CLA. See the CLA reminder comment above.
  • ❗ The changelog CI check is failing. This PR likely needs a changelog entry (e.g., .changes/ or CHANGES.md depending on the repo convention). Please check the CI log and add the required changelog file.

Automated review by github-manager-bot

@github-actions github-actions Bot removed the Stale label Jul 12, 2026
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.

4 participants