Skip to content
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

Refrains From Explicitly Requesting New OCR Rounds #11656

Merged
merged 2 commits into from
Jan 5, 2024
Merged

Conversation

kalverra
Copy link
Collaborator

We shouldn't change the API value and explicitly ask for a new round. This can cause weird behavior and flakes.

@kalverra kalverra requested a review from a team as a code owner December 22, 2023 14:12
Copy link
Contributor

I see that you haven't updated any CHANGELOG files. Would it make sense to do so?

@kalverra kalverra enabled auto-merge January 5, 2024 15:35
tateexon
tateexon previously approved these changes Jan 5, 2024
@cl-sonarqube-production
Copy link

SonarQube Quality Gate

Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@kalverra kalverra added this pull request to the merge queue Jan 5, 2024
Merged via the queue into develop with commit 094b252 Jan 5, 2024
78 checks passed
@kalverra kalverra deleted the removeOCRRequest branch January 5, 2024 16:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants