Skip to content

Commit 6021afc

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into mrb_03_19_2024_python_deprecation
2 parents e886120 + 4a4efbc commit 6021afc

File tree

5 files changed

+73
-42
lines changed

5 files changed

+73
-42
lines changed

articles/ai-services/openai/includes/whisper-python.md

Lines changed: 31 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,34 @@ pip install openai==0.28.1
3838

3939
1. Replace the contents of quickstart.py with the following code. Modify the code to add your deployment name:
4040

41-
```python
41+
# [OpenAI Python 1.x](#tab/python-new)
42+
43+
```python
44+
import os
45+
from openai import AzureOpenAI
46+
47+
client = AzureOpenAI(
48+
api_key=os.getenv("AZURE_OPENAI_API_KEY"),
49+
api_version="2024-02-01",
50+
azure_endpoint = os.getenv("AZURE_OPENAI_ENDPOINT")
51+
)
52+
53+
deployment_id = "YOUR-DEPLOYMENT-NAME-HERE" #This will correspond to the custom name you chose for your deployment when you deployed a model."
54+
audio_test_file = "./wikipediaOcelot.wav"
55+
56+
result = client.audio.transcriptions.create(
57+
file=open(audio_test_file, "rb"),
58+
model=deployment_id
59+
)
60+
61+
print(result)
62+
```
63+
64+
# [OpenAI Python 0.28.1](#tab/python)
65+
66+
67+
68+
```python
4269
import openai
4370
import time
4471
import os
@@ -61,7 +88,9 @@ pip install openai==0.28.1
6188
)
6289

6390
print(result)
64-
```
91+
```
92+
93+
---
6594

6695
Run the application with the python command on your quickstart file:
6796

articles/data-factory/concepts-pipelines-activities.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: data-factory
88
ms.subservice: orchestration
99
ms.custom: synapse
1010
ms.topic: conceptual
11-
ms.date: 10/20/2023
11+
ms.date: 03/11/2024
1212
---
1313

1414
# Pipelines and activities in Azure Data Factory and Azure Synapse Analytics
@@ -30,6 +30,10 @@ Azure Data Factory and Azure Synapse Analytics have three groupings of activitie
3030

3131
An input dataset represents the input for an activity in the pipeline, and an output dataset represents the output for the activity. Datasets identify data within different data stores, such as tables, files, folders, and documents. After you create a dataset, you can use it with activities in a pipeline. For example, a dataset can be an input/output dataset of a Copy Activity or an HDInsightHive Activity. For more information about datasets, see [Datasets in Azure Data Factory](concepts-datasets-linked-services.md) article.
3232

33+
> [!NOTE]
34+
> There is a default soft limit of maximum 80 activities per pipeline, which includes inner activities for containers.
35+
36+
3337
## Data movement activities
3438

3539
Copy Activity in Data Factory copies data from a source data store to a sink data store. Data Factory supports the data stores listed in the table in this section. Data from any source can be written to any sink.

articles/service-bus-messaging/service-bus-resource-manager-exceptions.md

Lines changed: 9 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,15 @@
11
---
2-
title: Azure Service Bus Resource Manager exceptions | Microsoft Docs
3-
description: List of Service Bus exceptions surfaced by Azure Resource Manager and suggested actions.
2+
title: Azure Service Bus Resource Manager exceptions
3+
description: This article provides a list of Service Bus exceptions surfaced by Azure Resource Manager and suggested actions.
44
ms.topic: article
55
ms.custom: devx-track-arm-template
6-
ms.date: 10/25/2022
6+
ms.date: 03/19/2024
77
---
88

99
# Service Bus Resource Manager exceptions
1010

1111
This article lists exceptions generated when interacting with Azure Service Bus using Azure Resource Manager - via templates or direct calls.
1212

13-
> [!IMPORTANT]
14-
> This document is frequently updated. Please check back for updates.
15-
1613
Here are the various exceptions/errors that are surfaced through the Azure Resource Manager.
1714

1815
## Error: Bad Request
@@ -23,7 +20,7 @@ Here are the various exceptions/errors that are surfaced through the Azure Resou
2320
| ---------- | ------------- | ------------- | ----------- | -------------- |
2421
| Bad Request | 40000 | Sub code=40000. The property *'property name'* can't be set when creating a Queue because the namespace *'namespace name'* is using the 'Basic' Tier. This operation is only supported in 'Standard' or 'Premium' tier. | On Azure Service Bus Basic Tier, the below properties can't be set or updated - <ul> <li> RequiresDuplicateDetection </li> <li> AutoDeleteOnIdle </li> <li>RequiresSession</li> <li>DefaultMessageTimeToLive </li> <li> DuplicateDetectionHistoryTimeWindow </li> <li> EnableExpress (not supported in Premium too)</li> <li> ForwardTo </li> <li> Topics </li> </ul> | Consider upgrading from Basic to Standard or Premium tier to use this functionality. |
2522
| Bad Request | 40000 | Sub code=40000. The value for the 'requiresDuplicateDetection' property of an existing Queue(or Topic) can't be changed. | Duplicate detection must be enabled/disabled at the time of entity creation. The duplicate detection configuration parameter can't be changed after creation. | To enable duplicate detection on a previously created queue/topic, you can create a new queue/topic with duplicate detection and then forward from the original queue to the new queue/topic. |
26-
| Bad Request | 40000 | Sub code=40000. The specified value 16384 is invalid. The property 'MaxSizeInMegabytes', must be one of the following values: 1024;2048;3072;4096;5120. | The MaxSizeInMegabytes value is invalid. | Ensure that the MaxSizeInMegabytes is one of the following - 1024, 2048, 3072, 4096, 5120. |
23+
| Bad Request | 40000 | Sub code=40000. The specified value 16384 is invalid. The property `MaxSizeInMegabytes` must be one of the following values: 1024;2048;3072;4096;5120. | The MaxSizeInMegabytes value is invalid. | Ensure that the MaxSizeInMegabytes is one of the following - 1024, 2048, 3072, 4096, 5120. |
2724
| Bad Request | 40000 | Sub code=40000. Partitioning can't be changed for Queue/Topic. | Partitioning can't be changed for entity. | Create a new entity (queue or topic) and enable partitions. |
2825
| Bad Request | none | The namespace *'namespace name'* doesn't exist. | The namespace doesn't exist within your Azure subscription. | To resolve this error: <ul> <li> Ensure that the Azure Subscription is correct. </li> <li> Ensure the namespace exists. </li> <li> Verify the namespace name is correct (no spelling errors or null strings). </li> </ul> |
2926
| Bad Request | 40000 | Sub code=40000. The supplied lock time exceeds the allowed maximum of '5' minutes. | The time for which a message can be locked must be between 1 minute (minimum) and 5 minutes (maximum). | Ensure that the supplied lock time is between 1 min and 5 mins. |
@@ -36,16 +33,16 @@ Here are the various exceptions/errors that are surfaced through the Azure Resou
3633

3734
## Error code: 429
3835

39-
Just like in HTTP, "Error code 429" indicates "too many requests". It implies that the specific resource (namespace) is being throttled because of too many requests (or due to conflicting operations) on that resource.
36+
Just like in HTTP, "Error code 429" indicates too many requests. It implies that the specific resource (namespace) is being throttled because of too many requests (or due to conflicting operations) on that resource.
4037

4138
| Error code | Error sub code | Error message | Description | Recommendation |
4239
| ---------- | ------------- | ------------- | ----------- | -------------- |
4340
| 429 | 50004 | Sub code=50004. The request was terminated because the namespace *your namespace* is being throttled. | This error condition is hit when the number of incoming requests exceed the limitation of the resource. | Wait for a few seconds and try again. <br/> <br/> Learn more about the [quotas](service-bus-quotas.md) and [Azure Resource Manager request limits](../azure-resource-manager/management/request-limits-and-throttling.md)|
4441
| 429 | 40901 | Sub code=40901. Another conflicting operation is in progress. | Another conflicting operation is in progress on the same resource/entity | Wait for the current in-progress operation to complete before trying again. |
45-
| 429 | 40900 | Sub code=40900. Conflict. You're requesting an operation that isn't allowed in the resource's current state. | This condition may be hit when multiple requests are made to perform the operations on the same entity (queue, topic, subscription, or rule) at the same time. | Wait for a few seconds and try again |
42+
| 429 | 40900 | Sub code=40900. Conflict. You're requesting an operation that isn't allowed in the resource's current state. | This condition might be hit when multiple requests are made to perform the operations on the same entity (queue, topic, subscription, or rule) at the same time. | Wait for a few seconds and try again |
4643
| 429 | 40901 | Request on entity *'entity name'* conflicted with another request | Another conflicting operation is in progress on the same resource/entity | Wait for the previous operation to complete before trying again |
47-
| 429 | 40901 | Another update request is in progress for the entity *'entity name'*. | Another conflicting operation is in progress on the same resource/entity | Wait for the previous operation to complete before trying again |
48-
| 429 | none | Resource Conflict Occurred. Another conflicting operation may be in progress. If this operation is a retry for failed operation, background cleanup is still pending. Try again later. | This condition may be hit when there's a pending operation against the same entity. | Wait for the previous operation to complete before trying again. |
44+
| 429 | 40901 | Another update request is in progress for the entity: `<entity name>`. | Another conflicting operation is in progress on the same resource/entity | Wait for the previous operation to complete before trying again |
45+
| 429 | none | Resource Conflict Occurred. Another conflicting operation might be in progress. If this operation is a retry for failed operation, background cleanup is still pending. Try again later. | This condition might be hit when there's a pending operation against the same entity. | Wait for the previous operation to complete before trying again. |
4946

5047

5148
## Error code: Not Found
@@ -61,7 +58,7 @@ This class of errors indicates that the resource wasn't found.
6158

6259
## Error code: Internal Server Error
6360

64-
This class of errors indicates that there was an internal server error
61+
This class of errors indicates that there was an internal server error.
6562

6663
| Error code | Error sub code | Error message | Description | Recommendation |
6764
| ---------- | ------------- | ------------- | ----------- | -------------- |

0 commit comments

Comments
 (0)