azure-sdk-for-js
azure-sdk-for-js copied to clipboard
[arm-machinelearning] Incorrect JobBaseDetails mapper
- @azure/arm-machinelearning
The bug description
Hello, I wanted to use your new package, but I found a small problem with it. When trying to create a job, I got an error about an invalid request body. At first, I thought that I made a mistake myself, but I double-checked.

As you can see from the screenshot:
- The payload that I created for the start of the job.
- The payload that request got after mapping
This happened because this mapper doesn't have the required for me fields, at least:
- environmentId;
- command;
- codeId;
If you will fix it as soon as possible - it will be great for my project, thanks
Label prediction was below confidence level 0.6
for Model:ServiceLabels
: 'Docs:0.07501003,Azure.Core:0.064508736,Compute - VM:0.05811521'
I will take a look earlier next week.
@turdigicode Thanks for bringing this up! I reproduced this issue in my local and will be back to you soon!
@turdigicode We found this is a known issue and we'll release a new package to fix it.
@kazrael2119 Could you help release a new package?
Hi @turdigicode , We fixed this bug ,here is the new SDK: azure-arm-machinelearning-2.0.0.zip
You can vertify whether the SDK resolve your issue in your local environment. If it is good for you, please tell me, because we will release this new SDK version : https://github.com/Azure/azure-sdk-for-js/pull/22819.
Thanks
@MaryGao Can you finish the release and provide the new version here? Thanks
@turdigicode We released one version to fix this issue, Could you try the latest 2.0.0 version?
Feel free to let us know if this issue still exists!
Hi @turdigicode. 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.
close it as resolved. @turdigicode feel free to reopen it if you still found any issues about it. Thanks