Reduce ExtractWorkflowNameFromFile overhead by removing deferred close path#34777
Merged
Conversation
Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com>
Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix performance regression in ExtractWorkflowNameFromFile
Reduce May 25, 2026
ExtractWorkflowNameFromFile overhead by removing deferred close path
pelikhan
approved these changes
May 25, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR targets a performance regression in BenchmarkExtractWorkflowNameFromFile by removing the deferred Close() path in extractWorkflowNameFromFile, and it updates the smoke Antigravity workflow to run awf using an explicit JSON config file.
Changes:
- Refactored
extractWorkflowNameFromFileto close the file explicitly rather than viadefer, aiming to reduce overhead in a hot path. - Updated
.github/workflows/smoke-antigravity.lock.ymlto generate anawf-config.jsonand invokeawfwith--config.
Show a summary per file
| File | Description |
|---|---|
| pkg/cli/workflows.go | Refactors workflow-title extraction to avoid deferred close overhead. |
| .github/workflows/smoke-antigravity.lock.yml | Switches awf invocation to use a generated --config JSON file. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 1
Comment on lines
+413
to
+415
| if closeErr != nil { | ||
| return "", fmt.Errorf("failed to close workflow file %s: %w", filePath, closeErr) | ||
| } |
Collaborator
|
@copilot review and resolve all comments. |
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Contributor
Author
Addressed the review feedback and pushed a fix in commit I updated |
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.
BenchmarkExtractWorkflowNameFromFileregressed materially versus historical runtime (+35.3%). The hotspot is the per-call file handling path inextractWorkflowNameFromFile.What changed
extractWorkflowNameFromFileto use explicit close sequencing instead of deferred close + named return mutation.Why this matters for the regression
Code change (core)