BF: Fix erronious alert when using any local transcriber#7258
Merged
TEParsons merged 1 commit intopsychopy:releasefrom May 21, 2025
Merged
BF: Fix erronious alert when using any local transcriber#7258TEParsons merged 1 commit intopsychopy:releasefrom
TEParsons merged 1 commit intopsychopy:releasefrom
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## release #7258 +/- ##
===========================================
+ Coverage 12.18% 12.24% +0.06%
===========================================
Files 346 347 +1
Lines 64010 64344 +334
===========================================
+ Hits 7800 7880 +80
- Misses 56210 56464 +254
🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Basically, we were checking for the key in
localTranscriebrsrather than the value, so it was always behaving as if an invalid transcriber was chosen & was showing an unnecessary alert.Fixes #7192