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

Fix "no tuning" value by "not tuned" #1913

Merged
merged 1 commit into from
Oct 9, 2023
Merged

Fix "no tuning" value by "not tuned" #1913

merged 1 commit into from
Oct 9, 2023

Conversation

arbulu89
Copy link
Contributor

@arbulu89 arbulu89 commented Oct 9, 2023

Description

By mistake I used the no tuning backend value when it should be not tuned.
I just used the frontend value 🤦

How was this tested?

Old tests are working

@arbulu89 arbulu89 added the bug Something isn't working label Oct 9, 2023
@arbulu89 arbulu89 force-pushed the fix-not-tuned-typo branch from 04e226a to 70ab238 Compare October 9, 2023 07:24
@arbulu89 arbulu89 force-pushed the fix-not-tuned-typo branch from 70ab238 to 052fe18 Compare October 9, 2023 07:47
@arbulu89 arbulu89 marked this pull request as ready for review October 9, 2023 08:07
Copy link
Member

@EMaksy EMaksy left a comment

Choose a reason for hiding this comment

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

Ah damn, also slipped trough my eyes :D
LGTM, let's merge and i push the other fix based on this fix!

@arbulu89 arbulu89 merged commit 4b4fc8a into main Oct 9, 2023
@arbulu89 arbulu89 deleted the fix-not-tuned-typo branch October 9, 2023 11:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

Successfully merging this pull request may close these issues.

2 participants