[smoke-otel-tracing] OTEL smoke: jest flag silently skipped, diagnostic path mismatch, api-proxy spans unverified
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, observability
Research direction
Start with .github/workflows/smoke-otel-tracing.md and its compiled .lock.yml; compare the Jest command and diagnostic log paths, then trace the api-proxy log host mapping from containers/api-proxy/otel.js. The issue reports that --testPathPatterns passes 75 tests. Confirm the mapping and span output in the post-step; done when the workflow fails on Jest errors, reads the correct log, and verifies api-proxy spans and token attributes.
Written by the indexing model from the issue text.
Description
Smoke run 44409831996 (PR #11794) found three defects in .github/workflows/smoke-otel-tracing.md and its compiled .lock.yml.
1. Test step never runs tests (unexpected failure)
The "Run api-proxy OTEL tests" step runs npx jest --verbose --ci --testPathPattern='otel' 2>&1 || true. The installed Jest (30.1.3) rejects --testPathPattern with Option "testPathPattern" was replaced by "--testPathPatterns" and exits 1. The || true hides this, so the step reports success with no tests run.
Running npx jest --ci --testPathPatterns='otel' in containers/api-proxy passes: 3 suites, 75/75 tests (otel.test.js, otel-fanout.test.js, otel-workload-identity.test.js).
Fix: use --testPathPatterns in both the .md and .lock.yml, and remove || true so a failing invocation fails the step.
2. Diagnostic path mismatch
smoke-otel-tracing.mdpost-step reads/tmp/gh-aw/sandbox/firewall/logs/api-proxy/otel.jsonl.- The compiled
.lock.ymlreads/tmp/gh-aw/sandbox/firewall/logs/api-proxy-logs/otel.jsonl.
The api-proxy writes /var/log/api-proxy/otel.jsonl inside the container (containers/api-proxy/otel.js). Confirm the host mapping, fix the source, and recompile.
3. api-proxy span export not verified
At agent time, /tmp/gh-aw/sandbox/firewall/logs was empty. The only exported span was gh-aw.agent.setup (in /tmp/gh-aw/otel.jsonl), not an api-proxy request span, so no gen_ai.usage.* attributes were observed. The post-step runs after the agent, so confirm span export and token attributes in that step's output for this run.
Passing scenarios
otel.jsloads;isEnabled()returnstrue; exports includestartRequestSpan,setTokenAttributes,endSpan,endSpanError,shutdown.- Env forwarding:
GITHUB_AW_OTEL_TRACE_IDandGITHUB_AW_OTEL_PARENT_SPAN_IDinenv-passthrough.ts;GH_AW_OTLP_ENDPOINTS,OTEL_EXPORTER_OTLP_ENDPOINT, and both trace IDs inapi-proxy-env-config.ts. onUsagehook present incontainers/api-proxy/token-tracker-http.js.
📡 OTel tracing validated by Smoke OTel Tracing
Add label ready-for-aw to run again
- expires on Nov 25, 2026, 10:37 PM UTC
- Dominant language
- TypeScript
- Stars
- 165
- Forks
- 84
- Avg merge
- 5h 57m
- Merged PRs (30d)
- 390
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/gh-aw-firewall
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
github/gh-aw-firewall#11797 ·
Maintainers usually reply within 1 day
-
awf-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/gh-aw-firewall#11612 ·
Maintainers usually reply within 1 day
-
agentic-workflows automated dependencies
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/gh-aw-firewall#3837 ·
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 3/5 1-2 days Newbie friendliness 48/100
github/gh-aw-firewall#11802 ·
Maintainers usually reply within 1 day
-
automation otel smoke-test tracing
Difficulty 1/5 Under an hour Newbie friendliness 1/100
github/gh-aw-firewall#11801 ·
Maintainers usually reply within 1 day
All issues in github/gh-aw-firewall
Similar issues
-
bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Potential Bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Comfy-Org/ComfyUI_frontend#23773 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 85/100
lingdojo/kana-dojo#34301 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
code-yeongyu/senpi#7007 ·
Maintainers usually reply within 1 day
-
area/renderer bug plugin/echarts priority/P3
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day