Repository navigation
test(parity): write the CALLS edge dump to a file, not stdout - #1442
Merged
Merged
Conversation
#1441 printed the whole CALLS edge set as a single JSON line per backend (~650 entries, ~100 KB). GitHub truncated the step log as a result, so the Actions output stopped after the first backend's STATS_JSON and neither the comparison table nor the new diagnostics were visible — the opposite of the intent. The subprocess now writes its edge list to <temp_test_dir>/<backend>_calls_edges.json and the parent reads that, leaving only the small human-readable diff in the log. Local run: log is 12 KB with a longest line of 831 chars (was ~100 KB on one line), and the diagnostics print in full. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Hi! 👋 Join our CodeGraphContext Discord channel to collaborate: https://discord.gg/dR4QY32uYQ |
github-project-automation
Bot
moved this from Backlog tasks
to Done
in CGC Progress Board
Contributor
🔍 PR Code Graph Analysistest(parity): write the CALLS edge dump to a file, not stdout (#1442) 📊 Interactive VisualizationView the blast radius graph: PR Reviewer Dashboard 📦 ArtifactsThe graph JSON has been uploaded as a build artifact: Generated by CodeGraphContext using FalkorDB Lite |
This branch was successfully deployed
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
1 participant
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.
Fixes a problem I introduced in #1441.
#1441 printed each backend's whole CALLS edge set as a single JSON line (~650 entries, ~100 KB). GitHub truncated the step log as a result — the Actions output stopped right after the first backend's
STATS_JSON, so neither the comparison table nor the new diagnostics were visible. Exactly the opposite of the intent.The subprocess now writes its edge list to
<temp_test_dir>/<backend>_calls_edges.jsonand the parent reads that file, leaving only the small human-readable diff in the log.Verified locally:
and the diagnostics still print in full: