PR: Fix Profiler error when run is stopped #6238
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #6220.
This pull request addresses a few aspects of the issue reported.
When the
Stop
button was clicked when a profile was running, Spyder still attempted to display the profiler results even know there wouldn't have been any. The profiler only writes results when it finishes. The fix is to recognize the button event and display a different text to the user, along with clearing the datatree.The
load_data
method in theProfilerDataTree
class assumed that the default results file existed, but if the run had been canceled, then this file doesn't exist. A try/except was added to this to catch file errors. Note that item 1 should prevent this from being called.