Users started to see this error after a restart of the Linux server.
Bitbucket Server could not create the merge diff for this pull request. To resolve this warning you could try to push a new commit to update the pull request, attempt to merge the pull request anyway...
Manually pulling the PR as a fix isn't something we want to do moving forward.
I looked at the logs and it shows Please clone 'X', checkout 'Y' and merge 'Z' (or commit '1da27846f205f3a54c8270d355716e61d86c7ddd') manually, resolving any conflicts, and push the result.
a bit further in the logs says
Caused by: com.atlassian.bitbucket.scm.CommandFailedException: '/usr/bin/git merge -m Automatic merge --no-ff --no-log --allow-unrelated-histories 1da27846f205f3a54c8270d355716e61d86c7ddd' exited with code 128 saying: error: add_cacheinfo failed to refresh for path 'src/Common/Utilities/Serializers/LevelEditor/CompartmentV2.h'; merge aborting.
Caused by: com.atlassian.utils.process.ProcessException: Non-zero exit code: 128