I had the following Scenario:
1) Local changes and commit on Feature Branch
2) Push changes to Feature Branch on Bitbucket
3) Create Pull Request from Feature Branch -> master
4) Add some changes and push them to Feature Branch
Now I expect that the pull request is updated by the new commit. I did not see any new commit that is pushed to Bitbucket after the creation of the Pull Request.
We use Bitbucket Data Center Version 4.4.0. But we are planning to update in the next few weeks. Probably the issue is fixed by a newer Version?
Thanks in advance
Most of the time this behavior is caused by the event queue filling up and dropping events. The events that were dropped would have been the ones that rescoped the pull request to update it, but never happened since the event was dropped. If that is what's going on a search through the
RejectedExecutionException would have lines similar to the following:
java.util.concurrent.RejectedExecutionException: Task com.atlassian.sal.core.executor.ThreadLocalDelegateRunnable@1ab334c1 rejected from java.util.concurrent.ThreadPoolExecutor@1f6328e4
[Running, pool size = 4, active threads = 4, queued tasks = 4096, completed tasks = 7743]
If you see this, have a read through RejectedExecutionException to help identify the cause or apply the workaround.
If you're not seeing that message, feel free to raise a support request at https://support.atlassian.com and we'll take a closer look.
In addition to checking what @Jeff Thomas said, please also have a look at the KB below:
Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs