Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AutoML throws several OperationCanceledExceptions #4821

Closed
zeroskyx opened this issue Feb 10, 2020 · 4 comments
Closed

AutoML throws several OperationCanceledExceptions #4821

zeroskyx opened this issue Feb 10, 2020 · 4 comments
Labels
P1 Priority of the issue for triage purpose: Needs to be fixed soon.

Comments

@zeroskyx
Copy link

Greetings,

when using any AutoML API project such as Sentiment Analysis for User Reviews, several exceptions are thrown in the background.

This is probably due to some internal cancellation and has no additional negative impacts but is pretty ugly in the debugger.

Would it be feasible to wrap this cancellation in a Task.ContinueWith() in order to keep the debugger clean?

Keep up the great work!

@frank-dong-ms-zz frank-dong-ms-zz added the P1 Priority of the issue for triage purpose: Needs to be fixed soon. label Feb 10, 2020
@frank-dong-ms-zz
Copy link
Contributor

frank-dong-ms-zz commented Feb 10, 2020

Thanks for reporting this.
I tried run the BinaryClassification_AutoML sample project and below is my console output, no exceptions found:
image

Can you provide a screenshot of these exceptions and your system information?

@zeroskyx
Copy link
Author

Thanks for the fast response -- the exceptions are only visible with a debugger attached and "Just my code" disabled.

I have a screenshot of the example using VSCode and with "justMyCode": false, in launch.json:

image

@frank-dong-ms-zz
Copy link
Contributor

I debugged this issue a little bit, this exception is thrown by this line: https://github.com/dotnet/machinelearning/blob/master/src/Microsoft.ML.Data/DataLoadSave/Binary/BinarySaver.cs#L219, this OperationCanceledException is an internal signalling mechanism of BlockingCollection so it is safe to ignore them. The exception is handled by the framework code and you wouldn't have noticed it if you hadn't had your debugger configured to intercept it.

You can reference to this post as more info: https://stackoverflow.com/questions/22967631/how-can-blockingcollectiont-getconsumingenumerable-throw-operationcanceledex/35848060

@frank-dong-ms-zz
Copy link
Contributor

Close this issue as this is expected behavior, thanks

@dotnet dotnet locked as resolved and limited conversation to collaborators Mar 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P1 Priority of the issue for triage purpose: Needs to be fixed soon.
Projects
None yet
Development

No branches or pull requests

2 participants