Uh oh!
There was an error while loading. Please reload this page.
Use charting venv in API consumption report - #53675
Merged
Merged
Conversation
Contributor
PR TriageCategory: chore (WIP) | Risk: low | Priority: low (score 20)
Recommended action: defer — recheck once agent finishes and diff is populated
|
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
CopilotAI
changed the title
[WIP] Fix missing tools for chart generation in GitHub API Consumption Report AgentUse charting venv in API consumption reportAug 18, 2026
pelikhan
marked this pull request as ready for review
August 18, 2026 12:39
Contributor
There was a problem hiding this comment.
Pull request overview
Updates chart execution to target the prepared virtualenv, but that interpreter is incompatible with the agent sandbox’s glibc version.
Changes:
- Uses the charting virtualenv interpreter explicitly.
- Regenerates workflow metadata.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/api-consumption-report.md | Updates chart execution instructions. |
.github/workflows/api-consumption-report.lock.yml | Refreshes the generated body hash. |
Review details
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
Suppressed comments (1)
.github/workflows/api-consumption-report.md:417
- The sub-agent is also told that this host-created venv will be executable, but the linked run directly tested this exact path and it failed with a glibc 2.38/2.35 mismatch. Update this instruction only after provisioning a Python environment that is compatible with the agent container; otherwise the generated script still cannot be executed.
/tmp/gh-aw/python/venv/bin/python3 /tmp/gh-aw/python/api_consumption_charts.py
- Files reviewed: 2/2 changed files
- Comments generated: 1
- Review effort level: Balanced
| Use the `chart-script-writer` agent to write `/tmp/gh-aw/python/api_consumption_charts.py`, | ||
| then run it: `python3 /tmp/gh-aw/python/api_consumption_charts.py`. | ||
| then run it with the prepared charting environment: `/tmp/gh-aw/python/venv/bin/python3 /tmp/gh-aw/python/api_consumption_charts.py`. |
Contributor
🎉 This pull request is included in a new release. Release: |
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 freeto 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.
The API consumption report workflow provisions scientific Python charting libraries in
/tmp/gh-aw/python/venv, but the agent prompt ran chart generation with barepython3. In the reported run, that resolved to a PyPy interpreter without matplotlib/pandas/numpy/scipy.