[GitHub] tysonnorris commented on issue #4134: the `processAcknowledgement` may process `CompletionMessage` first for blocking incovation even the message is sent ahead of `ResultMessage`

[GitBox <gi...@apache.org>]

tysonnorris commented on issue #4134: the `processAcknowledgement` may process `CompletionMessage` first for blocking incovation even the message is sent ahead of `ResultMessage`
URL: https://github.com/apache/incubator-openwhisk/issues/4134#issuecomment-442920066
 
 
   I ran into similar, and think it is due to: 
   ```
   Future[Unit] = {
     AcknowledegmentMessage.parse(raw) match {
      ...<message handling in any order>...
     }
   }
   ```
   In my case, I'm trying to ensure the activation db lookup is not done at controller, and disabling that db lookup locally makes the "first" activation fail - seems like the initial message parse is slower than subsequent ones.
   Moving the Future below `AcknowledegmentMessage.parse(raw)` fixes it I think. I will see if #4135 fixes it as well.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services