Repository navigation
[Follow-up to #49368] Recover incoming pyamqp windows and resolve changelogs - #49947
Closed
S.J. (cstolting-collab) wants to merge 203 commits into
Closed
S.J. (cstolting-collab) wants to merge 203 commits into
S.J. (cstolting-collab) wants to merge 203 commits into
Conversation
…Python-6914223 (Azure#49052) * Configurations: 'specification/storagediscovery/resource-manager/Microsoft.StorageDiscovery/StorageDiscovery/tspconfig.yaml', and CommitSHA: '320c9af356f887266debf5e78d28feca3a674c93' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6845274 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. * Configurations: 'specification/storagediscovery/resource-manager/Microsoft.StorageDiscovery/StorageDiscovery/tspconfig.yaml', and CommitSHA: 'f438548671e7f80bec48182a8428f4339d088337' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6880947 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. * Configurations: 'specification/storagediscovery/resource-manager/Microsoft.StorageDiscovery/StorageDiscovery/tspconfig.yaml', and CommitSHA: '6d8c4205a2065b9e0d463820a53a5e12e10e7db7' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6887285 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. * Configurations: 'specification/storagediscovery/resource-manager/Microsoft.StorageDiscovery/StorageDiscovery/tspconfig.yaml', and CommitSHA: '1a9e22f1580bc46451a66612a3286ea14540d8df' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6893538 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. * Configurations: 'specification/storagediscovery/resource-manager/Microsoft.StorageDiscovery/StorageDiscovery/tspconfig.yaml', and CommitSHA: '0799fda68aab1e2c6f5f0d06f028f451b14bf0a8' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6914223 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. --------- Co-authored-by: azure-sdk <azuresdk@microsoft.com>
…-6912810 (Azure#49305) * Configurations: 'specification/elasticsan/resource-manager/Microsoft.ElasticSan/ElasticSan/tspconfig.yaml', and CommitSHA: '8e41d2371ec5d559580031132a57ab250eca61aa' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6907765 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. * Configurations: 'specification/elasticsan/resource-manager/Microsoft.ElasticSan/ElasticSan/tspconfig.yaml', and CommitSHA: '0b8708e5213a35638b7d8627de4ea9b1735c31fb' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6912810 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. * Update CHANGELOG.md --------- Co-authored-by: azure-sdk <azuresdk@microsoft.com> Co-authored-by: ChenxiJiang333 <119990644+ChenxiJiang333@users.noreply.github.com>
… dev dependencies (Azure#49423) * Add issue-regen orchestrator skill and pre-install azure-ai-projects dev deps PR 49422 showed the issue-assigned cloud agent session for azure-ai-projects hit two separate problems when regenerating from a GitHub issue: 1. Dependency DNS failure: 'python -m pip install -r dev_requirements.txt', run as a required preflight step inside azure-ai-projects-emit-from-typespec, executes live in the agent's firewalled Bash-tool session and failed to resolve a package host. Pre-install it in copilot-setup-steps.yml instead, while the setup job still has full network access, mirroring the existing tsp-client pre-install added for the same reason. 2. No unattended orchestrator: azure-ai-projects-emit-from-typespec is written for an interactive human developer. It asks branch-name and TypeSpec-source questions one at a time and creates its own topic branch and PR (Steps 2-4 and 15), which conflicts with the working branch and draft PR that GitHub issue assignment already creates for a cloud agent session. Add azure-ai-projects-run-issue-regeneration, which validates the issue's 'TypeSpec commit' / 'Base branch' inputs, then runs the existing emit-from-typespec / author-samples / author-tests / update-changelog skills in order with explicit overrides for the already-assigned branch and PR, matching the pattern already used by the analogous run-issue-regeneration skill in azure-sdk-for-js's sdk/ai/ai-projects. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Scope azure-ai-projects dev dependency pre-install to its own branches The unconditional 'pip install -r sdk/ai/azure-ai-projects/dev_requirements.txt' step ran for every cloud agent session in this repo, regardless of task, paying its install cost (aiohttp, azure-mgmt-*, opentelemetry-sdk, etc.) even for work unrelated to azure-ai-projects. Gate it on the session's branch name instead, matching the actual naming GitHub's issue assignment uses for this package's regeneration workflow (e.g. 'copilot/azure-ai-projects-regenerate-<commit>', observed on PR Azure#49422). A plain branch-name check is used rather than a git merge-base ancestry check against origin/feature/azure-ai-projects/vnext, because actions/checkout's default shallow clone (fetch-depth: 1) does not reliably support ancestry checks without extra, non-trivial unshallowing. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Address Copilot code review findings - copilot-setup-steps.yml: dev_requirements.txt contains bare local paths (e.g. '../../core/azure-core') that pip resolves against the invoking working directory, not the requirements file's own directory. Running 'pip install -r sdk/ai/azure-ai-projects/dev_requirements.txt' from the repo root therefore failed before installing anything (confirmed by reproducing the exact error locally). Run it via a subshell with cwd set to the package directory instead, so the rest of the job keeps the repo root as its working directory. - SKILL.md: the PR-reuse guard checked for an existing PR and its base branch, but never required it to actually be OPEN and in draft, so a closed, merged, or ready-for-review PR could incorrectly pass. Require state == OPEN and isDraft == true explicitly. - SKILL.md: the final commit staged only CHANGELOG.md, but author-samples/author-tests don't commit their own edits, so any samples or tests they add would stay uncommitted and never reach the managed PR. Stage everything (excluding .env*) before that commit. - SKILL.md: emit-from-typespec's Steps 7/9/14 close their git commit -m quote right after the title, leaving a stray unmatched quote on the Co-authored-by line; executed as shown this breaks the shell. Added an override using two -m flags instead. Step 13's 'rmdir /s /q build' is a Windows cmd.exe command that doesn't run on this Linux session; added an override to use 'rm -rf build'. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Modify git push command and cleanup instructions Updated git push command to use 'HEAD' instead of a specific branch name. Adjusted cleanup command for Linux compatibility. Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> * Override tsp-client/pip calls inherited from emit-from-typespec; fix regex anchor - Step 1a's and Step 5's bare 'tsp-client' commands are not on PATH; only 'npm exec --prefix eng/common/tsp-client --no -- tsp-client ...' resolves to the package installed by copilot-setup-steps.yml. Verified both the repo-root form (Step 1a) and the sdk/ai/azure-ai-projects-relative form (Step 5) return the pinned 0.33.1 version via real bash. - Step 1g reruns 'pip install -r dev_requirements.txt' live. Direct URL requirements (the file's HTTPS wheel) are refetched by pip on every invocation regardless of whether the package is already installed, so this would hit the same unreachable host even though copilot-setup-steps already installed it. Override it to a no-op for this branch. - '\z' is not a valid end-of-string anchor in Bash ERE or Python 3.10's e module (that needs capital '\Z'); replaced with the portable '$' anchor. - Reorganized the overrides list into step order (1a, 1g, 2a, 2b, 3, 5, 7/9/14, 13, 15) now that it covers more steps. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Modify pip install steps for azure-ai-projects Updated pip install command to include editable install. Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> * Add offline changelog-version lookup and safe PR body file for regen skill - azure-ai-projects-update-changelog Step 2 calls the PyPI JSON API, but pypi.org is not reachable from this firewalled session. Override it to derive LATEST_PYPI_VERSION from the repository's own azure-ai-projects_* release tags via 'git ls-remote --tags' (lists ref names only, so it doesn't pull tag objects into what may be a shallow clone), filtered to stable X.Y.Z tags and sorted with 'sort -V'. Verified against the real repository tags: returns 2.8.0, matching PyPI's current info.version. - The final 'gh pr edit --body ...' step passes Markdown code spans (API names in backticks) through a double-quoted shell argument, letting Bash expand them as command substitutions and silently drop their contents. Write the description to a file with a quoted heredoc (disables all shell expansion) and pass it via --body-file instead. Verified the failure mode and the fix with a real bash reproduction. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Co-authored-by: glharper <glharper@users.noreply.github.com>
…zure#49431) * Enable uv native-TLS to fix UnknownIssuer cert errors downloading interpreters/packages on CI agents * Update eng/tools/azure-sdk-tools/ci_tools/venv.py Co-authored-by: Libba Lawrence <llawrence@microsoft.com> --------- Co-authored-by: Libba Lawrence <llawrence@microsoft.com>
Co-authored-by: azure-sdk <azuresdk@microsoft.com>
…oft.DataProtection/DataProtection/tspconfig.yaml', API Version: 2026-07-01, SDK Release Type: beta, and CommitSHA: 'b98dacf48388cade75dfa307cdb7fe64dcab0a2f' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6896043 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. (Azure#49255) Co-authored-by: azure-sdk <azuresdk@microsoft.com>
…/tspconfig.yaml', SDK Release Type: beta, and CommitSHA: '9162bb30e7dead5e941decd6fa2ee6879bf1a111' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6935729 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. (Azure#49444) Co-authored-by: azure-sdk <azuresdk@microsoft.com>
…49377) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Hameed Kunkanoor <41198503+Hameedkunkanoor@users.noreply.github.com>
…9025) * fix(agentserver): partition in-memory response state by user Scope response, item, history, and legacy execution state by the trusted platform user key. Preserve unkeyed local use in a separate anonymous partition and cover caller isolation, collisions, and cleanup. Authored-by: GitHub Copilot CLI 1.0.81-0 Model: GPT-6 Astra (gpt-6-astra) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 9e8471c6-fef7-46a5-9b42-d9e87f236721 * Regenerate AgentServer Responses API metadata Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: abe83751-b37b-4b0a-ade2-715927c28cc2 * fix(agentserver): partition file response storage by user Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: abe83751-b37b-4b0a-ade2-715927c28cc2 * Document file response store migration Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: abe83751-b37b-4b0a-ade2-715927c28cc2 * Address response partition review feedback Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: abe83751-b37b-4b0a-ade2-715927c28cc2 * Fix partition helper documentation checks Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: abe83751-b37b-4b0a-ade2-715927c28cc2 * Clarify anonymous file-store partition layout Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: abe83751-b37b-4b0a-ade2-715927c28cc2 * Align partition fix with next unreleased Responses version Preserve upstream published release notes, use matching 2.3.1 version and API metadata, and normalize the touched provider test formatting. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: abe83751-b37b-4b0a-ade2-715927c28cc2 * chore(agentserver): stage provider isolation as beta release Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: abe83751-b37b-4b0a-ade2-715927c28cc2 * fix(agentserver): align provider beta package classifier Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: abe83751-b37b-4b0a-ade2-715927c28cc2 --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 9e8471c6-fef7-46a5-9b42-d9e87f236721 Copilot-Session: abe83751-b37b-4b0a-ade2-715927c28cc2
…930784 (Azure#49299) * Configurations: 'specification/keyvault/resource-manager/Microsoft.KeyVault/KeyVault/tspconfig.yaml', API Version: 2026-05-15, SDK Release Type: stable, and CommitSHA: '80b3f7b9bdd7757783cfa8c35f06a299bd5dedad' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6907347 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. * Configurations: 'specification/keyvault/resource-manager/Microsoft.KeyVault/KeyVault/tspconfig.yaml', and CommitSHA: '3d13a66faf3cdca3fc4178de005faab79c7bcdad' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6922985 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. * Re-apply vaults.list() api-version customization after regeneration vaults.list() is a legacy paging API that must use api-version=2015-11-01 for both the initial and next-link requests. Regeneration resets the next-link param to the client's configured api-version, so re-apply the documented customization (see azure-sdk-for-python#43559, commit 6e09d1d). Fixes test_vaults_list_api_version and test_vaults_list_api_version_async. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 272efcb4-b315-43c3-89c0-03a3eac4fa39 * Update CHANGELOG.md * Configurations: 'specification/keyvault/resource-manager/Microsoft.KeyVault/KeyVault/tspconfig.yaml', and CommitSHA: 'be97609d55160e8d06e2fcbba9ddefbf2ee89bf8' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6930784 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. * Rename test_unittest.py to disable_test_unittest.py --------- Co-authored-by: azure-sdk <azuresdk@microsoft.com> Co-authored-by: Neerja Gangwar <ngangwar@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: ChenxiJiang333 <119990644+ChenxiJiang333@users.noreply.github.com> Copilot-Session: 272efcb4-b315-43c3-89c0-03a3eac4fa39
Co-authored-by: Rabah B <rboubchir+microsoft@microsoft.com> Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…#49459) Co-authored-by: azure-sdk <azuresdk@microsoft.com>
…re#49451) * fix(evaluation): export result status and pass state Include Microsoft-scoped execution status and boolean pass/fail fields in the existing Application Insights internal properties bag. Preserve null pass state for skipped and errored evaluations. Authored-by: GitHub Copilot CLI 1.0.81-11 Model: GPT-5.6 Sol (gpt-5.6-sol) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: dbfde7ba-9c78-42ae-9369-f2087ec2f917 * style(evaluation): match pinned black formatting Apply the exact Black 24.4.0 diff reported by the public PR pipeline. Authored-by: GitHub Copilot CLI 1.0.81-11 Model: GPT-5.6 Sol (gpt-5.6-sol) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: dbfde7ba-9c78-42ae-9369-f2087ec2f917 * fix(evaluation): align outcome attribute namespace Use gen_ai.evaluation for status and passed alongside existing evaluation fields. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: dbfde7ba-9c78-42ae-9369-f2087ec2f917 --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: dbfde7ba-9c78-42ae-9369-f2087ec2f917
…n - Python-6937855 (Azure#49428) * Configurations: 'specification/azureresiliencemanagement/resource-manager/Microsoft.AzureResilienceManagement/AzureResilienceManagement/tspconfig.yaml', API Version: 2026-10-01, SDK Release Type: stable, and CommitSHA: 'abfe7853f1382c8124b23be81984196102fd9343' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6931208 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. * Configurations: 'specification/azureresiliencemanagement/resource-manager/Microsoft.AzureResilienceManagement/AzureResilienceManagement/tspconfig.yaml', and CommitSHA: '639485c855d04eb485dc5a44d222477451d7dcb7' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6937855 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. * update Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * optimize changelog Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Update CHANGELOG.md --------- Co-authored-by: azure-sdk <azuresdk@microsoft.com> Co-authored-by: ChenxiJiang333 <v-chenjiang@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: ChenxiJiang333 <119990644+ChenxiJiang333@users.noreply.github.com>
* Bound management SDK breaking-change review requests Cap initial attribution work and trim oversized request suffixes with explicit omission counts. Preserve checked evidence and independently publish truncated reviews as partial. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 4650cdc2-5583-46a1-a425-53ad21b0482a * Temporarily enable manual management SDK review testing Uncomment the existing workflow_dispatch test entry point and regenerate the pinned lock. Keep actor restrictions and concurrency unchanged; disable again before merging. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 4650cdc2-5583-46a1-a425-53ad21b0482a * Disable temporary manual management SDK review testing Revert temporary dispatch enablement after successful testing. Restore the validated source and compiled lock while preserving the bounded-attribution fix. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 4650cdc2-5583-46a1-a425-53ad21b0482a * Fix spellcheck for jq review request filter Recognize the standard tojson jq builtin with a file-local cspell exception. The MCP Cspell check passed for all five review scripts with zero issues. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 4650cdc2-5583-46a1-a425-53ad21b0482a --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 4650cdc2-5583-46a1-a425-53ad21b0482a
…work/Network/tspconfig.yaml', SDK Release Type: stable, and CommitSHA: '88e2199d770d74f3061a162824185fd6894cb7d7' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6938423 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. (Azure#49455) Co-authored-by: azure-sdk <azuresdk@microsoft.com>
…on - Python-6938418 (Azure#49454) * Configurations: 'specification/liftrcommvault/Commvault.ContentStore.Management/tspconfig.yaml', API Version: 2026-09-30, SDK Release Type: stable, and CommitSHA: '88e2199d770d74f3061a162824185fd6894cb7d7' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6938418 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. * Update CHANGELOG.md * Update CHANGELOG.md --------- Co-authored-by: azure-sdk <azuresdk@microsoft.com> Co-authored-by: ChenxiJiang333 <119990644+ChenxiJiang333@users.noreply.github.com>
* Harden receipt dictionary normalization Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 3059c7ab-2e1e-46e4-8cd3-b248e1d25c70 * Normalize dictionaries inside nested lists in receipts Dictionaries inside nested lists skipped key normalization and the duplicate key check. Recurse through lists at any depth, and cover the nested cases in tests. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 3059c7ab-2e1e-46e4-8cd3-b248e1d25c70 --------- Co-authored-by: Yash Kumar <yakumar@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 3059c7ab-2e1e-46e4-8cd3-b248e1d25c70
…9692 (Azure#48999) * Configurations: 'specification/iothub/resource-manager/Microsoft.Devices/IoTHub/tspconfig.yaml', and CommitSHA: 'aacdbe71d42e2e79ff09699751c2d543e3ecc826' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6833416 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. * Configurations: 'specification/iothub/resource-manager/Microsoft.Devices/IoTHub/tspconfig.yaml', and CommitSHA: 'f18cd4935e28a80399a5e18201dc4b3ddfb20520' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6939692 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. --------- Co-authored-by: azure-sdk <azuresdk@microsoft.com> Co-authored-by: Davide Montanari <damontan@microsoft.com>
* Pre-install TypeSpec Python emitter's pinned black version in Copilot setup 'tsp-client update' shells out to the TypeSpec Python emitter (@azure-tools/typespec-python), which creates its own isolated venv and pip-installs a specific pinned 'black' version from its own dev_requirements.txt during code-generation formatting. That pin is versioned with whichever emitter release gets resolved for a given TypeSpec commit, so it isn't visible from this repository's own manifests, and the agent's firewalled session cannot reach the package index to fetch it live. A plain 'pip install' during setup would only warm pip's HTTP cache, which pip does not consult as a fallback when the package index itself is unreachable -- verified empirically: pip still fails after retrying the index 5 times, even with a matching wheel already cached. Instead, download the pinned wheel (black==26.3.1, matching https://github.com/Azure/typespec-azure/blob/main/packages/typespec-python/dev_requirements.txt) and its dependencies into a fixed directory, and persist PIP_FIND_LINKS pointing at it via GITHUB_ENV for the rest of the job, including the firewalled agent session. pip treats find-links entries as an extra local source alongside the index, so an exact-version match installs from there even when the index connection fails outright -- verified against a fully broken index connection (HTTPS_PROXY pointed at a refused port). Not scoped to azure-ai-projects: any package regenerated through tsp-client goes through the same Python emitter and can hit the same blocker. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Pre-download full TypeSpec Python emitter requirement set and verify offline install Co-authored-by: glharper <64209257+glharper@users.noreply.github.com> * Update pip download command in workflow Remove error suppression for pip download of dev requirements Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> * Gate Copilot setup pre-installs on azure-ai-projects branch; fix cspell - Add a shared "Detect azure-ai-projects branch" step (same git rev-parse + case-insensitive `*azure-ai-projects*` match the dev dependency pre-install already used) and gate the Node.js setup, tsp-client install, TypeSpec Python emitter Python dependency pre-install, and azure-ai-projects dev dependency pre-install on its output, so unrelated cloud agent sessions skip them. - Add `pygen` to the `.github/**` cspell override so the emitter pre-install step's comment and PYGEN_* variable names pass the spelling check (Build Analyze / "Check spelling (cspell)" was failing on them). - Drop the now-inaccurate "(any package, not just azure-ai-projects)" wording from the emitter pre-install step comment. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: d64d274e-b493-4d7c-b703-a48e331749be * Simplify Node.js setup by removing conditions Removed conditional checks for azure_ai_projects in setup steps. Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> * Update branch-check scope comment after un-gating Node/tsp-client/emitter Node.js, tsp-client, and the TypeSpec Python emitter pre-install are unconditional again (bd515e5), so only the azure-ai-projects dev dependency pre-install is gated on the shared branch check. Comment/log-message-only change, no behavior change: - Rewrite the "Detect azure-ai-projects branch" scope comment and log messages to describe only the dev dependency pre-install, and note why the other steps are intentionally not gated. - Restore the emitter pre-install comment's "(any package, not just azure-ai-projects)" wording, which is accurate again now that the step is repository-wide. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: d64d274e-b493-4d7c-b703-a48e331749be --------- Co-authored-by: glharper <glharper@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Copilot-Session: d64d274e-b493-4d7c-b703-a48e331749be
… port is absent (Azure#49344) * [Monitor Exporter] Fix "host:None" HTTP dependency target when server.port is absent * update Changelog * move changelog line to current version --------- Co-authored-by: Radhika Gupta <guptaradhika@microsoft.com>
* [EngSys] Add opt-in Rust native wheel build support Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 7ac28761-49fd-4c09-9885-101a72746ec0 * [EngSys] Fix spelling exceptions for native build documentation Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 7ac28761-49fd-4c09-9885-101a72746ec0 * [EngSys] Clarify native build pipeline requirements Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 7ac28761-49fd-4c09-9885-101a72746ec0 * Minor doc update * keep fallback * add azure-template-three * black * Revert azure-template-three fixture onboarding Revert aaf2e33 and its formatting follow-up e6fb68a. Remove the Rust fixture, generic PR exclusions, and fixture-driven version synchronization while preserving the original opt-in Rust build support. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8323733d-4446-4291-afcc-33c49f5afa86 * only install toolchain when needed, handle is compiled independently --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 7ac28761-49fd-4c09-9885-101a72746ec0 Copilot-Session: 8323733d-4446-4291-afcc-33c49f5afa86
… Python-6940910 (Azure#49463) * Configurations: 'specification/cognitiveservices/resource-manager/Microsoft.CognitiveServices/CognitiveServices/tspconfig.yaml', and CommitSHA: '8554bdf73142233b9584500c9661522d67380638' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6940910 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. * update * Update _patch.py * Update _patch.py --------- Co-authored-by: azure-sdk <azuresdk@microsoft.com> Co-authored-by: ChenxiJiang333 <v-chenjiang@microsoft.com> Co-authored-by: ChenxiJiang333 <119990644+ChenxiJiang333@users.noreply.github.com>
* Enable SSE keep-alives by default Co-authored-by: ankitbko <3169316+ankitbko@users.noreply.github.com> * Document default SSE keep-alive interval Co-authored-by: ankitbko <3169316+ankitbko@users.noreply.github.com> * Clarify Responses SSE keep-alive defaults Co-authored-by: ankitbko <3169316+ankitbko@users.noreply.github.com> * Bound SSE keep-alive source buffering Co-authored-by: ankitbko <3169316+ankitbko@users.noreply.github.com> * Revert "Bound SSE keep-alive source buffering" This reverts commit bcf61a8. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: ankitbko <3169316+ankitbko@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add agent snapshot lifecycle hooks Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add extensible snapshot lifecycle hooks Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix snapshot restore lifecycle state Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 700bada1-d4c1-4ee8-afec-f070643b1e38 * Refresh snapshot environment baseline Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 700bada1-d4c1-4ee8-afec-f070643b1e38 * Make restore retries fully idempotent Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 700bada1-d4c1-4ee8-afec-f070643b1e38 * Refresh restored process identities Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 700bada1-d4c1-4ee8-afec-f070643b1e38 * Pin restored process session affinity Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 700bada1-d4c1-4ee8-afec-f070643b1e38 * Redact session environment overrides from repr Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 700bada1-d4c1-4ee8-afec-f070643b1e38 * Add customizable readiness handler Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 700bada1-d4c1-4ee8-afec-f070643b1e38 * Timeout readiness server sample Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 700bada1-d4c1-4ee8-afec-f070643b1e38 * Keep readiness example in package README Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 700bada1-d4c1-4ee8-afec-f070643b1e38 * Update return type description for response Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> * Add snapshot lifecycle route aliases Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 700bada1-d4c1-4ee8-afec-f070643b1e38 * Rehydrate restored configuration and task leases Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 700bada1-d4c1-4ee8-afec-f070643b1e38 * Limit snapshot restore follow-up changes Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 700bada1-d4c1-4ee8-afec-f070643b1e38 * Update apiMdSha256 checksum in metadata file Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Copilot-Session: 700bada1-d4c1-4ee8-afec-f070643b1e38
Co-authored-by: Rabah B <rboubchir+microsoft@microsoft.com> Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…ctivation (Azure#49510) * AgentServer: integrate resilient tasks with memory snapshot session activation Separate process-side task registration from session-bound TaskManager construction and startup, so golden memory snapshots can be captured without a session-bound task runtime and activated after restore. - FOUNDRY_MEMORY_SNAPSHOT_ENABLED=false starts tasks during ordinary startup; absent or true defers startup to the after-restore hook. - Checkpoint initialization phases by restore ID, keep best-effort recovery, and wait for owned workers to stop before incompatible configuration rollback. - Responses propagates enabled-but-uninitialized task errors while activation is deferred and keeps the in-process fallback otherwise. - Add the design specification and compatibility notes. Replaces Azure#49485, which was closed when its base branch was deleted after Azure#49217 merged. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5e5a89f7-9dbe-4a5f-b98a-19c3246dc318 * Use absolute links to the design specification in package READMEs Package READMEs are published to PyPI, and the repository link guidance rejects relative links in them. Link to the specification with the same absolute blob/main form the Core README already uses for its other documents. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5e5a89f7-9dbe-4a5f-b98a-19c3246dc318 * Treat missing snapshot signal as cold startup and preserve resilience opt-out Only true defers enabled tasks until after-restore. Missing and false use ordinary startup. Align Responses fallback, cover all six flag/value combinations and active-session binding guards, and update capture-time signaling design and documentation. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5e5a89f7-9dbe-4a5f-b98a-19c3246dc318 * Preserve recoverable work during restore rollback and clean failed responses Join rollback workers before expiring their leases, preserving unfinished one-shot records and multi-turn input instead of terminal cancellation. Keep ordinary shutdown and explicit task cancellation unchanged. Remove exact caller-scoped response runtimes on deferred activation failure and isolate snapshot/session environment in tests. Add rollback retry and anonymous/named synchronous/background regressions; align design and changelogs. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5e5a89f7-9dbe-4a5f-b98a-19c3246dc318 * Stabilize restore retries and retain rollback worker ownership Record the materialization restore ID before recovery startup. Retain worker and lease handles before shutdown signalling so cooperative exits cannot bypass joining or lease release. Suppress steering promotion during rollback while preserving queued input for retry. Raise Responses minimum Core version to 2.3.0b2. Add matching-binding, cooperative shutdown, retained renewal and steering rollback regressions; update design and dependency documentation. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5e5a89f7-9dbe-4a5f-b98a-19c3246dc318 * Own task workers through completion and preserve deferred queue recovery Track execution, renewal, scanner and watchdog workers independently of active task entries so rollback joins workers whose handlers already completed. Reuse durable steering promotion to stage queued input for recovery without dispatching a new turn during cleanup. Add completed-handler renewal and normal-return queue regressions, and clarify lifecycle guarantees. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5e5a89f7-9dbe-4a5f-b98a-19c3246dc318 * Reset lifespan startup gate and reconcile interrupted rollback steering Reset task shutdown admission when a host enters a new lifespan. After rollback joins workers, reconcile suspended steering chains whose queued-input transition was cancelled. Reuse fenced drain bookkeeping with an explicit inactive lease claim, then expire that lease before restoring configuration. Add sequential lifespan and interrupted-drain regressions without dispatching another turn during cleanup. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5e5a89f7-9dbe-4a5f-b98a-19c3246dc318 * Resume failed task cleanup before restore activation retries Retain rollback reconciliation owners across transient storage errors and finish shielded cleanup under the original binding before rehydration or replacement startup. Cover repeated failures, committed claims, cancellation and shutdown without losing queued inputs. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5e5a89f7-9dbe-4a5f-b98a-19c3246dc318 * Retain restore rollback snapshots until cleanup completes Persist original environment and configuration through failed worker cleanup, restoring them before a retry computes its sparse override baseline. Cover omitted and repeated overrides across read/claim failures, cancellation, shutdown and later restores. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5e5a89f7-9dbe-4a5f-b98a-19c3246dc318 * Support task submissions from application restore handlers Prepare the session-bound TaskManager before the existing application callback and defer automatic recovery until dependencies are ready. Preserve task ownership, configuration compatibility, cached-restore readiness and sanitized rollback errors. Update the selected design and cover submission, recovery, retry and cancellation ordering. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5e5a89f7-9dbe-4a5f-b98a-19c3246dc318 * Align snapshot activation with independent protocol task enablement Use owning-host runtime requirements for cold and deferred activation, retain host/protocol scopes and bind recovery callbacks before preparation. Remove the remaining Responses dependency on the Invocations switch and cover protocol matrices, scoped recovery and deferred errors. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5e5a89f7-9dbe-4a5f-b98a-19c3246dc318 * Quiesce incompatible providers before same-session restore rollback Capture provider backend and location in pending rollback state and join incompatible workers before restoring configuration even when session identity matches. Preserve original-provider task records, cover endpoint/backend/root changes and clarify protocol opt-out and release history. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5e5a89f7-9dbe-4a5f-b98a-19c3246dc318 * Fence task admission and preserve complete rollback identity Bind runtimes to agent identity and resolved task storage, reject live identity changes before mutation, and settle accepted submissions before shutdown quiescence. Reject child admission during cancellation while preserving parent recovery and late-created lease handles. Cover identity, default HOME, in-flight producers and Responses no-fallback behavior. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5e5a89f7-9dbe-4a5f-b98a-19c3246dc318 * Preserve lease identity and defer steering callers across restore rollback Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5e5a89f7-9dbe-4a5f-b98a-19c3246dc318 * Preserve restore task ownership and sibling Core during CI package tests Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5e5a89f7-9dbe-4a5f-b98a-19c3246dc318 * Keep owned task leases consistent across compatible memory restores Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5e5a89f7-9dbe-4a5f-b98a-19c3246dc318 * Interrupt recovery reads before shutdown drains task admission Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5e5a89f7-9dbe-4a5f-b98a-19c3246dc318 * Track inline and positional task claims throughout admission Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5e5a89f7-9dbe-4a5f-b98a-19c3246dc318 --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5e5a89f7-9dbe-4a5f-b98a-19c3246dc318
Upgrade typing-extensions to 4.16.0 so CI dispatcher startup does not access typing.no_type_check_decorator, removed in Python 3.15. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…orizonDb/HorizonDb/tspconfig.yaml', and CommitSHA: '83261feee4b6975323d3fbec23c5152b308b2f94' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=7047864 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. (Azure#49868) Co-authored-by: azure-sdk <azuresdk@microsoft.com>
* Add opt-in Rust toolchain support to test pipelines Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * Decode captured native build logs as UTF-8 Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
* [DataAI] Rename ProblemDetails.detail to explanation - Regenerate from Azure/azure-rest-api-specs#47764 (1e290dceb1885c67ec8de95a094a6fda5e4f3303): ProblemDetails.detail is exposed as explanation in Python; the JSON property is still detail. - Keep the existing hand-edits that regeneration drops (safe unsupported-credential error, bytes request typing) and the existing pyproject.toml. - Update tests, CHANGELOG, api.md, and api.metadata.yml. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * [DataAI] Expose target_paths as list[str] - Pin tsp-location.yaml to Azure/azure-rest-api-specs#47800 (7521caa3f50a9a59225e136f8d2882ee66462e9c). Its model renames are C#-only; for Python, SemanticRerankingInferenceContent.target_paths becomes list[str] with commaDelimited encoding. - Keep the existing hand-edits and pyproject.toml that regeneration overwrites. - Switch the JSON sample to the model form; update tests, README, CHANGELOG, api.md, and api.metadata.yml. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * Pin typing-extensions 4.14.0 for Python 3.15 in CI tools The Python 3.15 test leg fails before any tests run: eng/scripts/dispatch_checks.py imports azure.core, and typing-extensions 4.12.2 reads typing.no_type_check_decorator, which Python 3.15 removed. Use 4.14.0 on Python 3.15 and keep 4.12.2 elsewhere, matching Azure#48845. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * Drop CI typing-extensions pins now that main pins 4.16.0 Azure#49915 pins typing-extensions==4.16.0 in eng/ci_tools.txt, which supports Python 3.15. The merge of main kept that pin alongside this branch's version-specific pins; together they can't be satisfied, which fails Prep Environment. Remove this branch's pins so eng/ci_tools.txt matches main. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
* Isolate authentication for multi-endpoint exports * Retrigger CI/CD pipeline
…ure#49368 Preserve EldertGrootenboer's outgoing-window implementation. Replenish incoming windows after dispatch, including handler failures, only for mapped sessions. Add 54 sync/async regression cases across both packages and merge current main without rewriting existing history. Validation: 386 focused pytest cases passed; pinned pylint 4.0.4 with Azure checker 0.5.7 passed. Tested tree 79d5144. No live-broker validation.
|
Azure Pipelines: 8 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
|
Thank you for your contribution S.J. (@cstolting-collab)! We will review the pull request and get back to you soon. |
3 tasks done
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.
This is a follow-up targeting the branch of #49368, not another competing PR against
main. It preserves EldertGrootenboer's outgoing-credit, fragmentation, and concurrency implementation.Reproduced gap
On #49368 head
8c13500388c7330820d53a7bac27c116cfedd339, a receive-side link handler exception bypasses incoming-window replenishment in both packages. The async unattached-handle path can also advertise fresh receive capacity during teardown.The added 54-case selection reproduced 36 failures on that baseline. The correction moves receive-window recovery into a post-dispatch
finallyblock, checksincoming_window <= 0, and only advertises capacity while the session isMAPPED. The original handler exception/cancellation is exercised with a successful FLOW send; failed FLOW sends are tested separately. No broader double-failure guarantee is asserted.Changes
mainatdadfa96d3e1d714a05e31fb4a43485b98e57b339and resolve the two changelog conflicts, preserving upstream entries and placing unpublished session-window fixes in the unreleased sections.Validation and limits
Published commit:
9af6fd068a787df8c4945f74d87646dcfa14b912.Tested and published tree:
79d5144770e19d4ec4a5767eb84628e6c6ef13d4.--noconftest --import-mode=importliband checked-out packages viaPYTHONPATH; no live-broker validation was run.The source-only correction is small; the merge also includes upstream history needed to resolve #49368's current merge conflicts. The original branch remains unchanged until its owner accepts this follow-up.