upgle opened a new pull request #4954:
URL: https://github.com/apache/openwhisk/pull/4954


   <!--- Provide a concise summary of your changes in the Title -->
   
   ## Description
   
   If the action is changed while the sequence action is executing, the old 
revision is referred to when the sub action is executed.
   
   At this time, if the server returns the latest revision, then a boxed error 
occurs due to an assert condition.
   
   ```scala
   assert(doc.rev.rev == null || doc.rev.rev == responseRev, "Returned revision 
should match original argument")        
   ```
   
   
![image](https://user-images.githubusercontent.com/5635513/91513275-e9dbac80-e91e-11ea-9f0d-2519bfb9ca27.png)
   
   To avoid this error, I've updated the code to retry with the latest code if 
the revision is different.
   
   ## Related issue and scope
   - https://github.com/apache/openwhisk/issues/4953
   
   ## My changes affect the following components
   - Invoker
   
   ## Types of changes
   <!--- What types of changes does your code introduce? Use `x` in all the 
boxes that apply: -->
   - Bug fix (generally a non-breaking change which closes an issue).
   
   ## Checklist:
   <!--- Please review the points below which help you make sure you've covered 
all aspects of the change you're making. -->
   
   - [x] I signed an [Apache 
CLA](https://github.com/apache/openwhisk/blob/master/CONTRIBUTING.md).
   - [x] I reviewed the [style 
guides](https://github.com/apache/openwhisk/wiki/Contributing:-Git-guidelines#code-readiness)
 and followed the recommendations (Travis CI will check :).
   - [x] I added tests to cover my changes.
   - [x] My changes require further changes to the documentation.
   - [x] I updated the documentation where necessary.
   
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to