Fix logs command not finding all runs when no workflow name is specified#2045
Merged
Fix logs command not finding all runs when no workflow name is specified#2045
Conversation
When no workflow name is specified, the logs command was incorrectly stopping iteration after the first batch if few agentic workflows were found, even when more runs were available from GitHub. Root cause: The end-of-data check was comparing the filtered runs count against batch size, instead of the total API response size. Fix: Modified listWorkflowRunsWithPagination to return both the filtered runs and the total count fetched from API, then use totalFetched for the end-of-data check instead of len(filtered runs). This ensures the command iterates until it finds the requested number of agentic workflow runs or truly reaches the end of GitHub data. Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Investigate logs command failure without workflow name
Fix logs command not finding all runs when no workflow name is specified
Oct 20, 2025
Contributor
|
Agentic Changeset Generator triggered by this pull request. |
pelikhan
reviewed
Oct 20, 2025
| @@ -0,0 +1,82 @@ | |||
| # Logs Command Filtering Fix | |||
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
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.
✅ COMPLETE: Fix logs command filtering issue
Problem
The
logscommand was not finding all workflow runs when no workflow name was specified:Root Cause
Bug in pagination logic (
pkg/cli/logs.goline 616):When searching all workflows:
len(filtered)=5 < batchSize=250→ STOP ❌ (incorrect!)totalFetched=250 < batchSize=250→ CONTINUE ✓Solution
Modified
listWorkflowRunsWithPaginationto return:Fixed iteration logic:
Changes Made
([]WorkflowRun, int, error)totalFetchedtracking before filteringtotalFetchedlogs_filtering_test.goValidation ✅
Impact
✅ Consistent behavior:
./gh-aw logs -c 10now returns 10 runs✅ No performance impact: Same efficient batch fetching
✅ No breaking changes: CLI interface unchanged
✅ Minimal code changes: Only 4 lines changed, rest are comments
✅ Well documented: Inline comments + test file
Files Changed
pkg/cli/logs.go- Core fix with detailed commentspkg/cli/logs_test.go- Updated test signaturepkg/cli/logs_filtering_test.go- Documentation testsTesting
All tests pass, no regressions detected.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.