Repository navigation
Fix Azure Government Speech routing and transcription errors (main hotfix) - #1948
Merged
Merged
Conversation
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
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
467921145f593b8704618e02fc8912e0a6528211. Main keeps its inline, SDK-only chat path; no Development Fast Transcription or absent Cosmos boundary-inventory machinery is imported.Known branch-flow blocker: This separate main-targeted hotfix PR was explicitly requested.
.github/workflows/enforce-branch-flow.ymlrejects main PRs unless their head isStaging; this PR is therefore expected to fail that check. No policy change/bypass, Staging modification, merge, or Azure deployment is authorized or performed.These are code-level fixes, not a confirmed diagnosis of a customer incident. No customer logs, deployed version, authentication mode, or exact failing workflow were available.
Linked issue
Refs #1946
Release Notes & Latest Features
Is this visible to end users?
Is this admin-facing (Admin Settings, governance, deployment, config)?
Should this become a Latest Feature card?
Screenshot needed for the card?
Version bump
application/single_app/config.pyVERSIONthird segment bumped, or not needed because this is docs-onlydeployers/version.txtbumped, or not needed becausedeployers/was not changedMain-local version:
0.261.064→0.261.065. No deployer files changed.Testing / validation
python -m pytest functional_tests\test_government_speech.py -q -p no:cacheprovider— passed, 2 fresh-process probes, native Speech SDK 1.47.0. Covers Government/custom endpoint retention, public/key compatibility, required configuration, normal speech/silence/end-of-stream, error/interrupt/timeout with partial results, late cancellation, start failure, real route responses, cleanup, and diagnostic privacy/sanitizer retention.python scripts\check_swagger_routes.py application\single_app\functions_documents.py application\single_app\route_backend_speech.py application\single_app\config.py— passed.python functional_tests\route_tests\test_route_blueprint_policy_inventory.py— passed, 6/6.python functional_tests\route_tests\test_route_unauthenticated_policy_contract.py— passed, 4/4.python functional_tests\route_tests\test_route_policy_test_coverage.py— passed, 2/2.python functional_tests\test_docs_app_surface_coverage.py— passed, 7/7, inventory current.python functional_tests\test_docs_site_quality.py— passed, 6/6.python -m py_compile application\single_app\functions_documents.py application\single_app\route_backend_speech.py application\single_app\config.py functional_tests\test_government_speech.py— passed.python -m compileall -q application\single_app— passed.git -c core.whitespace=blank-at-eol,blank-at-eof,space-before-tab,cr-at-eol diff --checkand the corresponding stageddiff --cached --check— passed.python -m pytest functional_tests\test_audio_ffmpeg_fallback.py -q -p no:cacheprovider— 6 passed, 2 pre-existing failures: stale exact-version assertions require app0.250.011and deployer1.0.21. Both were independently reproduced against unchanged HEAD sources, which contain0.261.064/1.0.32. Unrelated tests were not modified.No live Azure/RBAC/network or deployed Government recognition/synthesis smoke test was run. Offline native SDK checks do not establish deployment health. Main has no Cosmos response-boundary inventory/checker to refresh; no storage owner or response handling changed. Main's existing logger uses allowlisted
reasonrather than Development's newerfailure_codefield so diagnostic codes remain visible without broad logging changes.Documentation
Added
docs/explanation/fixes/AZURE_GOVERNMENT_SPEECH_FIX.mdand updated the Speech managed-identity setup guide. Release notes and issue progress comments are intentionally deferred to the coordinating session per the current request.Security checklist
@swagger_route(security=get_auth_security())sanitize_settings_for_user()No routes, settings payloads, frontend assets, or authorization policies were added or changed. Modified Speech error paths do not emit audio/transcripts, raw provider errors, access tokens, keys, or tracebacks.