Skip to content

Conversation

@Mihir-Mavalankar
Copy link
Contributor

PR Details

@Mihir-Mavalankar Mihir-Mavalankar self-assigned this Nov 10, 2025
@Mihir-Mavalankar Mihir-Mavalankar requested a review from a team as a code owner November 10, 2025 18:30
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Nov 10, 2025
@codecov
Copy link

codecov bot commented Nov 10, 2025

❌ 2 Tests Failed:

Tests completed Failed Passed Skipped
29563 2 29561 244
View the top 2 failed test(s) by shortest run time
tests.sentry.seer.autofix.test_issue_summary.TestRunAutomationStoppingPoint::test_with_feature_flag
Stack Traces | 4.31s run time
#x1B[1m#x1B[.../testutils/helpers/features.py#x1B[0m:215: in wrapped_method
    return method(*args, **kwargs)
#x1B[1m#x1B[.../hostedtoolcache/Python/3.13.1.../x64/lib/python3.13/unittest/mock.py#x1B[0m:1424: in patched
    return func(*newargs, **newkeywargs)
#x1B[1m#x1B[31mE   TypeError: TestRunAutomationStoppingPoint.test_with_feature_flag() missing 2 required positional arguments: 'score' and 'expected'#x1B[0m
tests.sentry.seer.autofix.test_issue_summary.TestRunAutomationStoppingPoint::test_without_feature_flag
Stack Traces | 4.59s run time
#x1B[1m#x1B[.../seer/autofix/test_issue_summary.py#x1B[0m:766: in test_without_feature_flag
    assert mock_trigger.call_args[1]["stopping_point"] is None
#x1B[1m#x1B[31mE   TypeError: 'NoneType' object is not subscriptable#x1B[0m

To view more test analytics, go to the Test Analytics Dashboard
📋 Got 3 mins? Take this short survey to help us improve Test Analytics.

event_id: str,
user_id: int | None,
auto_run_source: str,
stopping_point: AutofixStoppingPoint | None = None,
Copy link
Member

@JoshFerge JoshFerge Nov 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we're changing the signature of the task which could cause issues as old/new versions exist at the same time, but since we're adding a default to the parameter, this is okay. (we may want to add **kwargs to the signature for future in case a parameter gets removed)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I thought a default should be okay. I think I will keep as is for now because this will become a required parameter once the the fallback stuff is removed.

Copy link
Member

@JoshFerge JoshFerge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how does this change interact with what values people have configured?

JoshFerge
JoshFerge previously approved these changes Nov 10, 2025
@Mihir-Mavalankar
Copy link
Contributor Author

how does this change interact with what values people have configured?

Currently it does not. My next PR will have the UI change the completely removes that settings and turns automation into a on and off toggle.

return

stopping_point = None
if features.has("organizations:triage-signals-v0", group.organization):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm does this flag need to be a ProjectFeature, not an OrganizationFeature? then pass group.project instead

looks like this is tested, but i'm not familiar w/ how it's mocked under the hood

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why does it need to be a project feature?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm it not sure either. This said organization here so I went with organizationFeature.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also, is this feature registered? was that done in a separate PR?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or since this only applies to the Seer project should I change the feature in flagpole to be a project feature?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the flag checks project_id

what do you mean by this?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh... wait can an organization feature even filter on project_id?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://develop.sentry.dev/backend/application-domains/feature-flags/flagpole/

doesn't seem like it. @Mihir-Mavalankar can you double check these docs and make sure our flag usage is correct?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah that's right. I have changed it to a project feature now. Options PR is merged and manager is updated in this PR.

@Mihir-Mavalankar Mihir-Mavalankar enabled auto-merge (squash) November 10, 2025 21:25
@Mihir-Mavalankar Mihir-Mavalankar merged commit fa3d768 into master Nov 10, 2025
65 checks passed
@Mihir-Mavalankar Mihir-Mavalankar deleted the fixability-stop-for-autofix branch November 10, 2025 21:34
@sentry
Copy link

sentry bot commented Nov 10, 2025

Issues attributed to commits in this pull request

This pull request was merged and Sentry observed the following issues:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants