umustafi opened a new pull request, #3771:
URL: https://github.com/apache/gobblin/pull/3771

   Dear Gobblin maintainers,
   
   Please accept this PR. I understand that it will not be reviewed until I 
have checked off all the steps below!
   
   
   ### JIRA
   - [X] My PR addresses the following [Gobblin 
JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references 
them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
       - https://issues.apache.org/jira/browse/GOBBLIN-1907
   
   
   ### Description
   - [X] Here are some details about my PR, including screenshots (if 
applicable):
   When other participants complete a lease (not just acquire it) in the time 
that the current participant has attempted the lease, we will see a NULL 
`lease_acquisition_timestamp` and should appropriately handle the resulting 
value. This case was missed and we were only expecting another participant to 
have acquired the lease. 
   We also add warning logs for `JobExceptions` that can be hiding the stack 
trace of errors encountered in runtime. 
   
   ### Tests
   - [X] My PR adds the following unit tests __OR__ does not need testing for 
this extremely good reason:
   Tested behavior without change to see NPE and after updates the tests pass 
without any exceptions 
   
   ### Commits
   - [X] My commits all reference JIRA issues in their subject lines, and I 
have squashed multiple commits if they address the same issue. In addition, my 
commits follow the guidelines from "[How to write a good git commit 
message](http://chris.beams.io/posts/git-commit/)":
       1. Subject is separated from body by a blank line
       2. Subject is limited to 50 characters
       3. Subject does not end with a period
       4. Subject uses the imperative mood ("add", not "adding")
       5. Body wraps at 72 characters
       6. Body explains "what" and "why", not "how"
   
   


-- 
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.

To unsubscribe, e-mail: [email protected]

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

Reply via email to