Issue Summary

Bitbucket UI displays a null message when pull request merge operation has got timed out

This is reproducible on Data Center: (yes) / (no) Yes

Steps to Reproduce

1. To replicate the problem, clone a large repository (for ex. Linux), make changes to a large code file and create a pull request.
2. Reduce the default merge timeout parameter to say 3s. Add below parameter to bitbucket.properties file

    pullrequest.merge.timeout=3 

   Restart the server to get the changes to effect

3. Open the pull request and Merge it. The request gets time out on the Bitbucket UI.
4. You'll see a null message on the screem

Expected Results

Error message is to be displayed on pull request merge timeout

Actual Results

Null message is displayed on the screen

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available