-
Notifications
You must be signed in to change notification settings - Fork 10
Feat/hierarchical workflow tracing #73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
serglom21
wants to merge
9
commits into
getsentry:main
Choose a base branch
from
serglom21:feat/hierarchical-workflow-tracing
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
a1404f9
feat: implement hierarchical workflow tracing with single transaction…
serglom21 6c14dc2
docs: add PR description and update local development guide
serglom21 2f936e6
refactor: remove markdown docs and revert unnecessary Sentry disabling
serglom21 b844639
docs: remove LOCAL_DEVELOPMENT.md and TESTING_SUMMARY.md
serglom21 48a9a69
feat: implement smart workflow completion detection
serglom21 0d4b2ee
fix: add exception handling to prevent resource leaks in timer callbacks
serglom21 1a949de
refactor: extract WorkflowJobCollector module with feature flag support
serglom21 9e764dc
- Fetch total job count from GitHub API to ensure all jobs are captured
serglom21 4cad034
add tests
serglom21 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Potential bug: A hard-coded job count check
if len(self.workflow_jobs[run_id]) >= 5prevents workflows with fewer than 5 jobs from ever being processed, leading to data loss.Description: The workflow processing logic is only triggered for workflows with 5 or more jobs due to a hard-coded check:
if len(self.workflow_jobs[run_id]) >= 5. Workflows with fewer jobs will never meet this condition, and their tracing data will be permanently lost. The analysis notes that the repository's own CI workflow has only 4 jobs and would be ignored by this logic. A comment,For testing, we'll wait for 5 jobs, suggests this was intended for testing but affects production functionality. There is no fallback mechanism to process these smaller workflows.Suggested fix: Remove the hard-coded job count check. Instead, implement a more robust mechanism to determine workflow completion, such as using the
_is_workflow_completemethod which exists but is currently unused, or by waiting for a signal that all jobs for a given run have been received.severity: 0.8, confidence: 0.95
Did we get this right? 👍 / 👎 to inform future reviews.