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

OwTSNE: Don't catch errors during optimization #3580

Conversation

pavlin-policar
Copy link
Collaborator

Issue

Fixes #3548.

Catching errors during optimization and showing them in the error
message bar makes them difficult to report. Furthermore, no exceptions
should be thrown during optimization and if something does go wrong, we
need to fix it.

Description of changes

Remove the optimization_error.

Includes
  • Code changes
  • Tests
  • Documentation

@pavlin-policar pavlin-policar force-pushed the tsne-dont-catch-optimization-errors branch 2 times, most recently from 79595ef to 6a78e75 Compare February 4, 2019 18:05
Catching errors during optimization and showing them in the error
message bar makes them difficult to report. Furthermore, no exceptions
should be thrown during optimization and if something does go wrong, we
need to fix it.
@pavlin-policar pavlin-policar force-pushed the tsne-dont-catch-optimization-errors branch from 6a78e75 to bcbe2b0 Compare February 12, 2019 08:38
@pavlin-policar
Copy link
Collaborator Author

My best guess is that something was failing due to the way things were being mocked. This is superseded by #3604.

@pavlin-policar pavlin-policar deleted the tsne-dont-catch-optimization-errors branch February 15, 2019 15:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

TSNE widget error handling catches too many errors
1 participant