You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2017/07/25 07:50:03 UTC

[jira] [Created] (FLINK-7259) Match not exhaustive in TaskMonitor

Till Rohrmann created FLINK-7259:
------------------------------------

             Summary: Match not exhaustive in TaskMonitor
                 Key: FLINK-7259
                 URL: https://issues.apache.org/jira/browse/FLINK-7259
             Project: Flink
          Issue Type: Bug
          Components: Mesos
    Affects Versions: 1.3.1, 1.4.0
            Reporter: Till Rohrmann


Two matches are not exhaustive in the class {{TaskMonitor}}. This can lead to a {{MatchError}}, potentially restarting this actor (depending on the supervision strategy).

{code}
 /Users/uce/Code/flink/flink-mesos/src/main/scala/org/apache/flink/mesos/scheduler/TaskMonitor.scala:157: warning: match may not be exhaustive.
[WARNING] It would fail on the following input: TASK_KILLING
[WARNING]       msg.status().getState match {
[WARNING]                    ^
[WARNING] /Users/uce/Code/flink/flink-mesos/src/main/scala/org/apache/flink/mesos/scheduler/TaskMonitor.scala:170: warning: match may not be exhaustive.
[WARNING] It would fail on the following input: TASK_KILLING
[WARNING]       msg.status().getState match {
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)