-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
fix(autofix): Poll for PR state #88832
Conversation
❌ 1 Tests Failed:
View the top 1 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
const [isPrProcessing, setIsPrProcessing] = useState(false); | ||
const [isBranchProcessing, setIsBranchProcessing] = useState(false); |
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.
could we make these conditions completely reliant on the autofix state instead of being react state? We can just rely on the changes step being in processing status right? Will make all this logic much simpler
If on the seer side we update the status before we return the call then the query invalidation inside onSuccess
should already receive a processing state next time it makes a request
@@ -99,7 +99,7 @@ export function useSelectSolution({groupId, runId}: {groupId: string; runId: str | |||
}; | |||
} | |||
); | |||
addSuccessMessage("Great, let's move forward with this solution."); | |||
addSuccessMessage('On it.'); |
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.
i like, much simpler
When creating a branch/PR, we now poll for the state instead of waiting for an API response. This should be more reliable.
When creating a branch/PR, we now poll for the state instead of waiting for an API response. This should be more reliable.