We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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?
Task.ContinueWith()
Keep up the great work!
The text was updated successfully, but these errors were encountered:
Thanks for reporting this. I tried run the BinaryClassification_AutoML sample project and below is my console output, no exceptions found:
Can you provide a screenshot of these exceptions and your system information?
Sorry, something went wrong.
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:
"justMyCode": false,
launch.json
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
Close this issue as this is expected behavior, thanks
No branches or pull requests
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!
The text was updated successfully, but these errors were encountered: