Azure ML extension throws warnings even after muting the warnings by only_show_errors about azure-cli-extensions HOT 6 OPEN

Thank you for opening this issue, we will look into it.

from azure-cli-extensions.

@eddmik

Thanks for bringing this to our attention. Those class messages are not errors, they're log warnings. All of our experimental classes are marked with a decorator to let users know that they are experimental, so that they don't use them in prod builds, or at the very least are cautious about doing so. This handled by a call to Python's logger and Python sends all logs to stderr; however, the --only-show-errors flag is implemented by Azure CLI (not our ml extension) and Azure CLI's own documentation explicitly says here that experimental warnings should be swallowed by that flag, so I'll assign this back to them to look at.

@yonzhan I've removed the ml labels

from azure-cli-extensions.

@diondrapeck I think from knack.log import get_logger's logger works with --only-show-errors.

@eddmik It is not recommended to use failOnStderr to determine the pipeline failure. See Azure/azure-cli#18372

from azure-cli-extensions.

@bebound thank you for your comment, I have read the comments, however it is only in the case where --debug is used it does not make sense to use the failOnStderr: true, in our case my understanding is, it makes sense to use failOnStderr: true in combination with --only-show-errors (See. Azure/azure-cli/issues/18372#issuecomment) please correct me if I am wrong. Otherwise how would you see that the job is failed?

from azure-cli-extensions.

@bebound Gotcha. I just checked and knack isn't GA yet, so due to Azure SDK for Python guidelines, we can't depend on it in our GA ML SDK (which the ml CLI extension is built on top of).

from azure-cli-extensions.

@bebound thank you for your comment, I have read the comments, however it is only in the case where --debug is used it does not make sense to use the failOnStderr: true, in our case my understanding is, it makes sense to use failOnStderr: true in combination with --only-show-errors (See. Azure/azure-cli/issues/18372#issuecomment) please correct me if I am wrong. Otherwise how would you see that the job is failed?

Use $LASTEXITCODE instead. The --only=show-errors option may not be reliable as any CLI dependency could write to stderr and interrupt your pipeline.

from azure-cli-extensions.