Skip to content

feat(autofix): Set default value for automated_run_stopping_point #93481

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

Merged
merged 1 commit into from
Jun 12, 2025

Conversation

seer-by-sentry[bot]
Copy link
Contributor

Fixes SEER-2N. The issue was that: Frontend sent null for field requiring literal string, causing Pydantic validation error in backend.

  • Ensures automated_run_stopping_point always has a value by setting a default of 'solution' if it's not provided in the input data.

This fix was generated by Seer in Sentry, triggered by Rohan Agarwal. 👁️ Run ID: 83104

Not quite right? Click here to continue debugging with Seer.

Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Jun 12, 2025
@roaga roaga marked this pull request as ready for review June 12, 2025 21:40
@roaga roaga requested a review from a team as a code owner June 12, 2025 21:40
@roaga roaga added the Trigger: getsentry tests Once code is reviewed: apply label to PR to trigger getsentry tests label Jun 12, 2025
@roaga roaga merged commit 1354398 into master Jun 12, 2025
44 of 45 checks passed
@roaga roaga deleted the seer/feat/autofix-default-stopping-point branch June 12, 2025 21:50
billyvg pushed a commit that referenced this pull request Jun 18, 2025
…93481)

Fixes
[SEER-2N](https://sentry.io/organizations/sentry/issues/5028696400/).
The issue was that: Frontend sent null for field requiring literal
string, causing Pydantic validation error in backend.

- Ensures `automated_run_stopping_point` always has a value by setting a
default of 'solution' if it's not provided in the input data.


This fix was generated by Seer in Sentry, triggered by Rohan Agarwal. 👁️
Run ID: 83104

Not quite right? [Click here to continue debugging with
Seer.](https://sentry.io/organizations/sentry/issues/5028696400/?seerDrawer=true)



### Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated
in the State of Delaware in 2015 as Functional Software, Inc. and is
gonna need some rights from me in order to utilize my contributions in
this here PR. So here's the deal: I retain all rights, title and
interest in and to my contributions, and by keeping this boilerplate
intact I confirm that Sentry can use, modify, copy, and redistribute my
contributions, under Sentry's choice of terms.

Co-authored-by: seer-by-sentry[bot] <157164994+seer-by-sentry[bot]@users.noreply.github.com>
andrewshie-sentry pushed a commit that referenced this pull request Jun 19, 2025
…93481)

Fixes
[SEER-2N](https://sentry.io/organizations/sentry/issues/5028696400/).
The issue was that: Frontend sent null for field requiring literal
string, causing Pydantic validation error in backend.

- Ensures `automated_run_stopping_point` always has a value by setting a
default of 'solution' if it's not provided in the input data.


This fix was generated by Seer in Sentry, triggered by Rohan Agarwal. 👁️
Run ID: 83104

Not quite right? [Click here to continue debugging with
Seer.](https://sentry.io/organizations/sentry/issues/5028696400/?seerDrawer=true)



### Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated
in the State of Delaware in 2015 as Functional Software, Inc. and is
gonna need some rights from me in order to utilize my contributions in
this here PR. So here's the deal: I retain all rights, title and
interest in and to my contributions, and by keeping this boilerplate
intact I confirm that Sentry can use, modify, copy, and redistribute my
contributions, under Sentry's choice of terms.

Co-authored-by: seer-by-sentry[bot] <157164994+seer-by-sentry[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: Frontend Automatically applied to PRs that change frontend components Trigger: getsentry tests Once code is reviewed: apply label to PR to trigger getsentry tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant