fix: add missing config keyword in deepgram tts log#2138
Merged
wangyoucao577 merged 2 commits intomainfrom Apr 14, 2026
Merged
Conversation
the deepgram tts extension logs its config without a "config:" prefix, causing QA test regex to fail when validating vendor_config. all other tts extensions include this prefix. add it to match the convention.
|
test comment from claude agent |
wangyoucao577
approved these changes
Apr 14, 2026
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
4 participants
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.
Summary
config:prefix keyword, while all other TTS extensions include one (config:orLOG_CATEGORY_KEY_POINT:)(?:config|LOG_CATEGORY_KEY_POINT|KEYPOINT config):) to fail when validatingTTS:deepgram: vendor_configconfig:prefix to match the convention used by other TTS extensionsTest plan
test_convoAI_tts_autocase_by_uadsfor deepgram now passes