Closed agribot2 closed 2 years ago
Hi @agribot2, thank you for opening an issue! I'm tagging some folks who should be able to help. For more context about the issue: https://github.com/MicrosoftDocs/azure-docs/issues/91074
Hi, Has this defect been considered by the team ? Has any decision been made about what to do next ? Thanks
@agribot2 Thanks for the feedback! We are currently investigating and will update you shortly.
@agribot2 I could see the same and it only runs for the first time. I am checking internally and get back to you.
I think the behavior is by design. If export_iteration was called twice, it will throw error for the second call. I guess we need two fixes; 1) fix the document so that the sample code calls get_export first to check if the iteration was already exported. 2) Fix the API error message. "...is already queued for export..." is not very clear.
@shonohs what steps are needed to re-export an iteration? If we check, and it was already exported, how do we export again?
You can use get_exports() to get a link to an exported model. We don't have API to force re-generate it. (Even if we had the API, new exported model will be exactly same as the old one.)
Hi @agribot2. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “/unresolve
” to remove the “issue-addressed” label and continue the conversation.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @areddish, @tburns10.
Author: | agribot2 |
---|---|
Assignees: | lmazuel, xiangyan99 |
Labels: | `question`, `Service Attention`, `Client`, `customer-reported`, `Cognitive - Custom Vision`, `issue-addressed` |
Milestone: | - |
Thank you for the suggestion that users must use the get_exports() method as a work-around for this defect. Allow me to say...
Having an API that work only once and fails if run a second time is poor quality.
However, given that there are work-arounds available I can understand the decision. I do hope that the team that manages the tutorial and example code at [https://docs.microsoft.com/en-us/azure/cognitive-services/custom-vision-service/export-programmatically](https://github.com/MicrosoftDocs/azure-docs/issues/url) now adds information about the defect and also provides example code that uses the get_exports() method to avoid the defect.
Thank you for clarifying the work-around.
Hi @agribot2. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “/unresolve
” to remove the “issue-addressed” label and continue the conversation.
Hi @agribot2, since you haven’t asked that we “/unresolve
” the issue, we’ll close this out. If you believe further discussion is needed, please add a comment “/unresolve
” to reopen the issue.
Describe the bug I am using an existing iteration in an existing custom vision project that has already correctly trained , classified images, etc I am trying download the azure customer vision model using python.
But the response is an error message that says ;- eaf41 redacted-3675c is already queued for export.
To Reproduce Steps to reproduce the behaviour:
1) Run the following python code (Taken from the Microsoft site ;- [https://docs.microsoft.com/en-us/azure/cognitive-services/custom-vision-service/export-programmatically](https://github.com/MicrosoftDocs/azure-docs/issues/url)
Actual behaviour / result;- The cloud based system causes the following error message ;- eaf41-redacted-3675c is already queued for export. No download is started.
Also, if the following different code is run MORE THAN ONCE, it only works as required the first time, but fails when run again. Taken from https://stackoverflow.com/questions/61097420/question-model-dowloading-with-custom-vision-python-api
Expected behaviour The system should download the iteration model to the user.
Screenshots N/A
Additional context The other method of downloading a model;- Manually via the web portal, works correctly. That interface works correctly even when tested using the same endpoint, keys, id's, project, training, publish and export functions that the python code targets.