You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/machine-learning/how-to-inference-server-http.md
+11-23Lines changed: 11 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -133,7 +133,7 @@ The following steps explain how the Azure Machine Learning inference HTTP server
133
133
There are two ways to use Visual Studio Code (VSCode) and [Python Extension](https://marketplace.visualstudio.com/items?itemName=ms-python.python) to debug with [azureml-inference-server-http](https://pypi.org/project/azureml-inference-server-http/) package.
134
134
135
135
1. User starts the AzureML Inference Server in a command line and use VSCode + Python Extension to attach to the process.
136
-
1. User sets up the `launch.json` in the VSCode and start the AzureML Inference Server within VSCode.
136
+
1. User sets up the `launch.json` in the VSCode and starts the AzureML Inference Server within VSCode.
137
137
138
138
**launch.json**
139
139
```json
@@ -167,13 +167,12 @@ TypeError: register() takes 3 positional arguments but 4 were given
167
167
168
168
```
169
169
170
-
You have **Flask 2** installed in your python environment but are running a version of `azureml-inference-server-http`
171
-
that does not support Flask 2. Support for Flask 2 is added in `azureml-inference-server-http>=0.7.0`, which is also in `azureml-defaults>=1.44`.
170
+
You have **Flask 2** installed in your python environment but are running a version of `azureml-inference-server-http` that doesn't support Flask 2. Support forFlask 2 is addedin`azureml-inference-server-http>=0.7.0`, which is also in`azureml-defaults>=1.44`.
172
171
173
-
1. If you are not using this package in an AzureML docker image, please use the latest version of
172
+
1. If you're not using this package in an AzureML docker image, use the latest version of
174
173
`azureml-inference-server-http` or `azureml-defaults`.
175
174
176
-
2. If you are using this package with an AzureML docker image, please make sure your are using an image built in or after July,
175
+
2. If you're using this package with an AzureML docker image, make sure you're using an image built in or after July,
177
176
2022. The image version is available in the container logs. You should be able to find a log similar to below:
178
177
179
178
```
@@ -186,32 +185,21 @@ that does not support Flask 2. Support for Flask 2 is added in `azureml-inferenc
The build date of the image appears after "Materialization Build", which in the above example is `20220708`, or July
190
-
8th, 2022. This is an image compatible with Flask 2. If you don't see a banner like this in your container log, your
191
-
image is out-of-date and should be updated. If you are using a cuda image, and are unable to find a newer image,
192
-
please check if your image is deprecated in [AzureML-Containers](https://github.com/Azure/AzureML-Containers). If it
193
-
is, you should be able to find replacements.
194
-
195
-
If this is an online endpoint, you can also find the logs under "Deployment logs"in the [online endpoint page in
196
-
Azure Machine Learning Studio](https://ml.azure.com/endpoints). If you deploy with SDK v1 and do not explicitly
197
-
specify an image in your deployment configuration, it will default to using a version of `openmpi4.1.0-ubuntu20.04`
198
-
that matches your local SDK toolset, which may not be the latest version of the image. For example, SDK 1.43 will
199
-
default to using `openmpi4.1.0-ubuntu20.04:20220616`, which is incompatible. Please make sure you use the latest SDK
200
-
for your deployment.
201
-
202
-
If for some reason you're unable to update the image, you can temporary workaround the issue by pinning
203
-
`azureml-defaults==1.43` or `azureml-inference-server-http~=0.4.13`, which will install the older version server with
204
-
`Flask 1.0.x`.
188
+
The build date of the image appears after "Materialization Build", which in the above example is `20220708`, or July 8, 2022. This image is compatible with Flask 2. If you don't see a banner like this in your container log, your image is out-of-date, and should be updated. If you're using a cuda image, and are unable to find a newer image, check if your image is deprecated in [AzureML-Containers](https://github.com/Azure/AzureML-Containers). If it is, you should be able to find replacements.
189
+
190
+
If this is an online endpoint, you can also find the logs under "Deployment logs" in the [online endpoint page in Azure Machine Learning studio](https://ml.azure.com/endpoints). If you deploy with SDK v1 and don't explicitly specify an image in your deployment configuration, it will default to using a version of `openmpi4.1.0-ubuntu20.04` that matches your local SDK toolset, which may not be the latest version of the image. For example, SDK 1.43 will default to using `openmpi4.1.0-ubuntu20.04:20220616`, which is incompatible. Make sure you use the latest SDK for your deployment.
191
+
192
+
If for some reason you're unable to update the image, you can temporarily avoid the issue by pinning `azureml-defaults==1.43` or `azureml-inference-server-http~=0.4.13`, which will install the older version server with `Flask 1.0.x`.
205
193
206
194
See also [Troubleshooting online endpoints deployment](how-to-troubleshoot-online-endpoints.md#error-resourcenotready).
207
195
208
-
### 2. I encountered an ``ImportError`` or ``ModuleNotFoundError`` on modules ``opencensus``, ``jinja2``, ``MarkupSafe``, or ``click`` during startup like the following:
196
+
### 2. I encountered an ``ImportError`` or ``ModuleNotFoundError`` on modules ``opencensus``, ``jinja2``, ``MarkupSafe``, or ``click`` during startup like the following message:
209
197
210
198
```bash
211
199
ImportError: cannot import name 'Markup' from 'jinja2'
212
200
```
213
201
214
-
Older versions (<= 0.4.10) of the server did not pin Flask's dependency to compatible versions. This is fixed in the latest version of the server.
202
+
Older versions (<= 0.4.10) of the server didn't pin Flask's dependency to compatible versions. This problem is fixed in the latest version of the server.
215
203
216
204
### 3. Do I need to reload the server when changing the score script?
0 commit comments