Skip to content

Conversation

@JLLeitschuh
Copy link
Member

Before we treated InterruptedExceptions just like every other
type of exception. This is bad because it means that the thread
that had been asked to exit was having to go through the process
of displaying a UI component which was causing deadlocks.

Closes #236

Before we treated InterruptedExceptions just like every other
type of exception. This is bad because it means that the thread
that had been asked to exit was having to go through the process
of displaying a UI component which was causing deadlocks.

Closes WPIRoboticsProjects#236
@JLLeitschuh JLLeitschuh added this to the v1.0.0 milestone Jan 3, 2016
@codecov-io
Copy link

Current coverage is 54.97%

Merging #240 into master will decrease coverage by -0.23% as of dfa8e45

@@            master    #240   diff @@
======================================
  Files          106     106       
  Stmts         3045    3063    +18
  Branches       342     348     +6
  Methods          0       0       
======================================
+ Hit           1681    1684     +3
- Partial        102     105     +3
- Missed        1262    1274    +12

Review entire Coverage Diff as of dfa8e45


Uncovered Suggestions

  1. +0.49% via ...cketPreviewView.java#90...104
  2. +0.46% via ...cketPreviewView.java#38...51
  3. +0.46% via .../ExceptionAlert.java#112...125
  4. See 7 more...

Powered by Codecov. Updated on successful CI builds.

ThomasJClark added a commit that referenced this pull request Jan 4, 2016
Fixes Handling of InterruptedExceptions
@ThomasJClark ThomasJClark merged commit af1c807 into WPIRoboticsProjects:master Jan 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants