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
fix: update django/psycopg/httpx for Python 3.13/3.14 compatibility
django:
- Add 5.1 for >=3.13 (4.2 doesn't support 3.13+)
- Fix test services: replace removed django.conf.urls.url with
django.urls.path (available since Django 2.0, works with 3.2+)
- Verified locally: django==5.1 PASSED with span validation on 3.13
psycopg:
- Add 3.2.* for >=3.13 (3.1.* has no cp313 binary wheels)
- Verified locally: psycopg[binary]==3.2.* PASSED with span validation on 3.13
httpx:
- Only test 0.23.* for >=3.13 (0.22.* can't install on 3.13+)
Update plugin-test skill with proxy bypass guidance.
Regenerate Plugins.md.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: .claude/skills/plugin-test/SKILL.md
+15-13Lines changed: 15 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -163,20 +163,22 @@ Plugin library failed to install in Docker. Check:
163
163
- Docker compose command for the service
164
164
165
165
### Failure - Permanent 502 / Empty Segments
166
-
If the consumer returns 502 indefinitely and no segments are collected:
166
+
**IMPORTANT: Check your HTTP proxy first!** If `http_proxy` or `https_proxy` environment variables are set, ALL test HTTP requests (prepare, validate) go through the proxy instead of reaching Docker containers directly. This causes 502 responses and empty segment data.
- Look for whether Flask actually started (should see `* Running on http://`)
169
-
- Common cause: `pip install -r requirements.txt` in the Docker container downgrades shared dependencies (urllib3, charset-normalizer) that break the Flask/agent startup
170
-
- Run `docker exec sw_<name>-consumer-1 pip list` to check installed package versions
171
-
- The Docker image has pre-installed packages from `make install`; test-specific `pip install` can create conflicts
172
-
173
-
### Local vs CI Differences
174
-
- CI runs on Linux with native Docker — faster, more reliable networking
175
-
- macOS Docker Desktop runs containers in a Linux VM — additional latency
176
-
- Some tests may fail locally due to dependency conflicts in containers but pass in CI where the environment is cleaner
177
-
- For authoritative span data verification, rely on CI results
0 commit comments