URL prediction error

[IgnacioHeredia]

Description

Deepaas returns an error when trying to predict an url after having predicted a file.
If this same url is being predicted at the beginning, just after having launched deepaas (and before having predicted a local file), the prediction runs just fine.

Steps to Reproduce

This error has been found while using the image classification model but this should be model independent as it is a deepaas error.

1. Launch deepaas
2. Try to predict a local file. You should get a json dict with your prediction.
3. Try to predict a URL.You get the following error:

400Undocumented | Error: BAD REQUEST
Response bodyDownload{ "message": "You must provide either 'url' or 'data' in the payload" }

Expected behavior:

If the url corresponded to an image you should get a json dict with the prediction from your model.

Actual behavior

Got a Bad Request error instead,

Versions

deepaas 0.2.1.dev1

[alvarolopez]

This is not a bug, but a limitation of the Swagger UI. If I understood it correctly you 1st performed a prediction using a file, then you made a prediction using the URL (both actions are done in a row, without reloading the page). The Swagger UI that Flask-RESTPlus provides us does not clean parameters that have been set between requests, therefore it is actually doing a prediction with two parameters (the leftover file, and the new URL). If you have a look before the 2nd call (i.e. with URL) you will see that the file is still there, thus the failure you get.