pip install pyazure -> azure#11
Merged
Merged
Conversation
joostdenijs
added a commit
that referenced
this pull request
Jun 7, 2012
pip install pyazure -> azure
AutorestCI
added a commit
that referenced
this pull request
Mar 13, 2019
NFSAAS-1875 Update to R3.5 Standard (#11)
AutorestCI
added a commit
that referenced
this pull request
Mar 20, 2019
…GA) (#4556) * Generated from 46f3cb6030777135484c1bdc4b1d2146053172f9 NFSAAS-1875 Update to R3.5 Standard (#11) * Generated from 084552639aef23de670f0dc26ba5c9496eb6daff Nfsaas 1875 swagger update (#12) * NFSAAS-1875 Update to R3.5 Standard * NFSAAS-1875 update to R3.5 standard * Generated from 0af27c76c27c57415609e59ba20027b3808ba30e Nfsaas 1875 swagger update (#13) * NFSAAS-1875 Update to R3.5 Standard * NFSAAS-1875 update to R3.5 standard * NFSAAS-1875 updated from review comments
lmazuel
pushed a commit
that referenced
this pull request
Mar 26, 2019
* [AutoPR netapp/resource-manager] Update to Release 3.5 standard (pre GA) (#4556) * Generated from 46f3cb6030777135484c1bdc4b1d2146053172f9 NFSAAS-1875 Update to R3.5 Standard (#11) * Generated from 084552639aef23de670f0dc26ba5c9496eb6daff Nfsaas 1875 swagger update (#12) * NFSAAS-1875 Update to R3.5 Standard * NFSAAS-1875 update to R3.5 standard * Generated from 0af27c76c27c57415609e59ba20027b3808ba30e Nfsaas 1875 swagger update (#13) * NFSAAS-1875 Update to R3.5 Standard * NFSAAS-1875 update to R3.5 standard * NFSAAS-1875 updated from review comments * Generated from c219e4e969a6443efa588eadc8ed77f611baa53e (#4638) Merge pull request #15 from leonardbf/NFSAAS-1875-correction NFSAAS-1875 small correction * updated versioning and change log * NFSAAS-2236 update python SDK tests for R3.5 (#4684) * Update HISTORY.rst
kristapratico
referenced
this pull request
in kristapratico/azure-sdk-for-python
Oct 19, 2019
pipeline ownership for queues and files
KieranBrantnerMagee
pushed a commit
to KieranBrantnerMagee/azure-sdk-for-python
that referenced
this pull request
Mar 30, 2020
…bus/track-2-stress-test-cleanup Kibrantn/servicebus/track 2 stress test cleanup
beltr0n
pushed a commit
to beltr0n/azure-sdk-for-python
that referenced
this pull request
Jan 22, 2021
…y-personal Added tests to identity package
wonder6845
pushed a commit
to wonder6845/azure-sdk-for-python
that referenced
this pull request
Aug 21, 2022
[keyvault] Migrate type comment to type annotation
5 tasks
This was referenced Apr 1, 2026
This was referenced Apr 14, 2026
sssash18
pushed a commit
that referenced
this pull request
May 20, 2026
Build 6327088 showed test_job_definition_job_run and test_start_c2c_job_with_private_source still failing on the mindependency leg with 'msrestazure.azure_exceptions.CloudError: InvalidAuthenticationToken'. Root cause: the floor-pinned azure-mgmt-storage (v2019_06_01) uses msrestazure transport which bypasses azure-core's RequestsTransport, and therefore the test-proxy, hitting live ARM instead of replaying the cassette. Detect the modernization line via the presence of the .aio submodule on azure-mgmt-storage/-network plus the v2022_04_01 namespace on azure-mgmt-authorization, and gate both cross-sub sync tests behind a pytest.mark.skipif that triggers when those signals are absent. The matrix-#11/#12/#13 schedule tests in the same file (which do not use cross-sub clients) are unaffected and continue to run in mindependency. The cross-sub imports themselves are now wrapped in try/except so the module collects cleanly when those packages are too old to even provide the symbols (otherwise mindependency would fail on the from-import line before the skipif could fire). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This was referenced May 25, 2026
sssash18
added a commit
that referenced
this pull request
Jun 12, 2026
* Add async and sync tests for Storage Mover management operations - Introduced async test suite for job runs operations, verifying list and get functionalities. - Added sync test suite for job runs operations with similar coverage. - Created async and sync tests for project operations, including create, get, update, and delete scenarios. - Implemented async and sync tests for storage mover operations, covering create, update, get, and delete functionalities. - Removed outdated async and sync operation tests that were not aligned with the new structure. * Update Storage Mover tests and configurations - Update asset tag in assets.json for versioning. - Enhance test sanitizers in conftest.py to avoid clobbering non-sensitive fields. - Skip agent-related tests that require a registered VM. - Modify job definition tests to accept scheduling variables for better flexibility. - Adjust assertions in storage mover tests to focus on specific tags rather than total counts. * Implement end-to-end tests for CloudToCloud job definitions with public and private sources in Storage Mover - Added async test for starting a CloudToCloud job with a public AWS S3 bucket as the source. - Implemented async test for starting a CloudToCloud job with a private AWS S3 bucket, including connection approval and RBAC setup. - Enhanced existing tests to provision necessary resources and validate job execution status. - Updated role assignment and resource cleanup logic to ensure proper teardown after tests. * test(storagemover): add cross-sub mgmt clients to dev_requirements Adds azure-mgmt-network, azure-mgmt-authorization, and azure-mgmt-storage as test-only dependencies. These are required by the cross-subscription flow exercised by matrix row #31 (test_start_c2c_job_with_private_source) and row #10's extended public-bucket E2E (test_job_definition_job_run): PE-connection approval on the shared PrivateLinkService, blob container provisioning under the shared storage account, and Storage Blob Data Contributor role assignment for the target endpoint MSI. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * test(storagemover): fix CI playback (sanitizer alignment + mindependency) Two CI failures from PR #47025: 1. Playback body mismatch on the regular Build Test legs: the custom cross-sub sanitizer rewrote the source literal b6b34ad8-... to 1111111-..., but the cassette already had 00000000-... (default AZURE_SUBSCRIPTION_ID sanitizer ran first at record time). Change the custom sanitizer target to 00000000-... so both sanitizers agree, no re-record needed. Also align role-assignment-GUID and principalId sanitizers to the same canonical value. 2. Collection error on mindependency/sdist legs: 'No module named azure.mgmt.storage.aio' — old floor-pinned azure-mgmt-storage lacks the .aio submodule. Guard the .aio imports in the async test file with pytest.importorskip so the module is skipped cleanly in that environment instead of failing collection. Local validation: full suite 60 PASS / 4 SKIP / 26s in playback with no AZURE_SUBSCRIPTION_ID env set (mimics CI). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * test(storagemover): skip cross-sub sync tests on mindependency leg Build 6327088 showed test_job_definition_job_run and test_start_c2c_job_with_private_source still failing on the mindependency leg with 'msrestazure.azure_exceptions.CloudError: InvalidAuthenticationToken'. Root cause: the floor-pinned azure-mgmt-storage (v2019_06_01) uses msrestazure transport which bypasses azure-core's RequestsTransport, and therefore the test-proxy, hitting live ARM instead of replaying the cassette. Detect the modernization line via the presence of the .aio submodule on azure-mgmt-storage/-network plus the v2022_04_01 namespace on azure-mgmt-authorization, and gate both cross-sub sync tests behind a pytest.mark.skipif that triggers when those signals are absent. The matrix-#11/#12/#13 schedule tests in the same file (which do not use cross-sub clients) are unaffected and continue to run in mindependency. The cross-sub imports themselves are now wrapped in try/except so the module collects cleanly when those packages are too old to even provide the symbols (otherwise mindependency would fail on the from-import line before the skipif could fire). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * test(storagemover): pin cross-sub mgmt client api_versions Build 6327280 reproduced a new failure mode on the whl + sdist CI legs (mindependency now passes after the previous skip-marker landed): Playback failure -- Uri doesn't match: request <...?api-version=2025-08-01> record <...?api-version=2025-06-01> Root cause: my local recording environment had azure-mgmt-storage 24.0.1 (default api-version 2025-06-01); CI's whl/sdist venvs pull the latest released azure-mgmt-storage 25.0.0 (default 2025-08-01). URL mismatch -> cassette miss -> proxy returns 404. Pin api_version explicitly on the cross-sub clients to the versions captured in the recordings: - StorageManagementClient -> '2025-06-01' - NetworkManagementClient -> '2025-05-01' - AuthorizationManagementClient already pinned via the v2022_04_01 namespace import (no kwarg needed) Applied to all 4 affected test methods (sync + async * #10 + #31). The recordings themselves are unchanged. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Suyash Choudhary <choudharysu@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
RaviPidaparthi
added a commit
that referenced
this pull request
Jun 18, 2026
…pec 024 Phase 5) Lands the §A APPROVED set of public-surface simplifications in a single coherent commit per Principle XII §4 non-duplication. Closes Phase 5 of spec 024 (responses re-design). ## Approved proposals applied - #4 — `max_pending` option DELETED. - #5 — `context.is_shutdown_requested` property DELETED (subsumed by #11's new `context.shutdown: asyncio.Event`). - #6 + #10 — `context.durability.*` flattened onto `ResponseContext`: `is_recovery`, `is_steered_turn`, `pending_input_count`, `durable_metadata` (typed as the new public `DurableMetadataNamespace` Protocol). - #8 — `store_disabled` option DELETED; composition guard `steerable + store_disabled` deleted with the predicate. - #11 — cancellation surface alignment (composing causes): `context.cancel: asyncio.Event` + `context.shutdown: asyncio.Event` + `context.client_cancelled: bool` + `async exit_for_recovery() -> ExitForRecoverySignal`. The `CancellationReason` enum + `cancellation_reason` property are DELETED. Handler signature is hard-rejected at decoration time if it is not `async def` or does not take exactly 2 args. - #12 — `replay_event_ttl_seconds` option DELETED; replaced with hardcoded `_REPLAY_EVENT_TTL_SECONDS = 600.0` constant in `hosting/_routing.py` (B35 ≥ 10 min replay verified GREEN). - #13 — `DurabilityEntryMode` Literal alias + `entry_mode` field DELETED. Recovery detection is now `context.is_recovery`. The `_map_entry_mode` helper is replaced by `_is_recovered_entry`. ## Source changes - `azure/ai/agentserver/responses/_options.py`: deleted parameters and composition guard. - `azure/ai/agentserver/responses/_response_context.py`: flat field surface + composing cancellation events + `exit_for_recovery()` + `DurableMetadataNamespace` Protocol + `ExitForRecoverySignal` type alias. Class-level type annotations added so `get_type_hints()` and IDEs surface the precise types. - `azure/ai/agentserver/responses/_durability_context.py`: `DurabilityContext` class + `DurabilityEntryMode` alias DELETED. `_DeveloperMetadataFacade` retained as internal impl. - `azure/ai/agentserver/responses/__init__.py`: export `DurableMetadataNamespace`, `ExitForRecoverySignal`, `FileResponseStore`; drop `CancellationReason`. - `azure/ai/agentserver/responses/models/runtime.py`: `CancellationReason` enum DELETED. - `azure/ai/agentserver/responses/hosting/_routing.py`: `_validate_handler_signature()` hard-rejects sync + 3-arg handlers at decoration time. `_dispatch_create` invokes with 2 args. `_configure_streams_registry` uses the hardcoded TTL constant. Decorator + dispatch surface aligned with the new contract. - `azure/ai/agentserver/responses/hosting/_endpoint_handler.py`: cancel-bridge sets `context.client_cancelled` / `context.shutdown` instead of stamping `cancellation_reason`. Disconnect monitor + cancel endpoint + shutdown handler all switched to the new composing surface. `_create_response_context` aliases `context.cancel` with the execution-context cancellation signal. - `azure/ai/agentserver/responses/hosting/_durable_orchestrator.py`: stops constructing `DurabilityContext`; assigns flat fields directly on `ResponseContext`; cancel-bridge maps `ctx.shutdown` → `context.shutdown.set() + cancel.set()` and `ctx.cancel` (steering pressure) → `cancel.set()` ONLY (no cause flag). `_map_entry_mode` replaced by `_is_recovered_entry` boolean helper. - `azure/ai/agentserver/responses/hosting/_orchestrator.py`: terminal routing reads `context.shutdown.is_set()` / `context.client_cancelled` instead of the deleted enum. All 3 `self._create_fn(...)` invocations updated to 2-arg. ## Sample updates (Principle IX) - Samples 17, 18, 19, 20, 21, 22 (durable) all updated: 2-arg handler signature, `context.cancel.is_set()` cancellation observation, flat `context.is_recovery` / `context.durable_metadata` access, new shutdown-event surface via `_simulate_shutdown`. - Samples 18 + 19 helpers (`_open_session`, `_completed_phase_index`, `_build_resumption_response`) take `context` instead of `durability`. - All 17 samples import cleanly. ## Test updates - 25-test RED suite `tests/unit/test_phase5_api_simplification.py` — ALL GREEN. - Obsolete `tests/unit/test_cancellation_reason.py` + `tests/unit/test_durability_context.py` DELETED. - `tests/unit/test_durable_orchestrator.py` rewritten for `_is_recovered_entry` + flat-context model. - Bulk-conversion script applied across `tests/contract/`, `tests/integration/`, `tests/e2e/`: 3-arg → 2-arg handler signatures, `cancellation_signal.X` → `context.cancel.X`, `context.cancellation_reason == X` → cause-boolean checks, `context.durability.X` → flat field equivalents. - Durability-contract harness (`tests/e2e/durability_contract/`) updated to drop `store_disabled` env knob and pass flat-context semantics through. ## Final test results - Unit: 617/617 GREEN. - Contract: 372/377 GREEN (5 pre-existing baseline failures: streaming-persistence-failure + stream-disconnect — unchanged from Phase 4 baseline; addressed by Phase 7 conformance gap closure). - Integration: 39/39 GREEN. - Interop: 62/62 GREEN. - E2e (excluding hosted-only): 188/189 GREEN (1 skip). - Durability-contract suite: 37/37 GREEN. - Total: 1315/1320 GREEN (5 pre-existing baseline). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
RaviPidaparthi
added a commit
that referenced
this pull request
Jul 1, 2026
… preset parity (spec 037 #1/#11) GREEN for 54a95ae. Reject max_attempts>10 and max_delay>1h at construction (fail-fast, not clamp). Align module-level exponential_backoff/fixed_delay wrappers to their classmethod values so zero-arg presets match the .NET port. Document caps + canonical preset values in SOT §15. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
3 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.
No description provided.