-
Bug
-
Resolution: Timed out
-
High
-
343
-
Severity 2 - Major
-
132,354
-
Issue Summary
Sometimes recent commits that exist on the remote repository are not visible in the website, in the 'Commits' page of the repo.
This impacts users' ability to open Pull requests: if a user wants to open a PR for an affected branch, they won't be able to, as no commits will show for this branch.
Steps to Reproduce
There are no steps to reproduce this, this issue rarely occurs in some repos
Workaround
Users have reported that pushing another commit or a new branch to the repo, solves the issue.
You can also contact Bitbucket Cloud Support (https://support.atlassian.com/contact/#/) to fix the issue for your repository.
Update (October 2021):
We have found the race condition that was responsible for this issue. While we couldn't fully eliminate it in the short-term we were able to significantly reduce its probability. Additionally, we have implemented it in such a way that we can easily fine-tune the parameters of the fix based on the customer impact. Please let us know here if you continue to be impacted by this issue and in the meantime please refer to the Workaround section above to unblock your workflow.
For a long-term solution we have recently kicked off a project to fix the issue fully, but this is a larger project and will take us some time to complete.
Update (June 2023):
We have been actively monitoring this issue and we are happy to see that the issue has been impacting our customers at a much lower pace over the last several months. We attribute this improved trajectory to numerous architectural improvements we were able to put in place over the last while. The issue is still occassionally reported but it is unclear now whether it still shares the same root cause as its original counterpart. As a result, we have decided to close this original issue and start tracking the symptoms under a new BCLOUD ticket. This will allow us to more easily track the influx of customer reports and focus on the latest possible root cause of the issue. If you experience these symptoms please report them under the new BCLOUD ticket.
https://jira.atlassian.com/browse/BCLOUD-22728
- relates to
-
-
- Closed
-
-
BBS-182532 You do not have permission to view this issue
-
-
- was split into
-
-
- Gathering Impact
-
- is related to
-
COREX-1412 Loading...
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
[BCLOUD-19548] Sometimes recent commits that exist on the remote repository are not visible in the website, in the 'Commits' page of the repo
| UIS | Original: 132084 | New: 132354 |
| Description |
Original:
h3. Issue Summary
Sometimes recent commits that exist on the remote repository are not visible in the website, in the 'Commits' page of the repo. This impacts users' ability to open Pull requests: if a user wants to open a PR for an affected branch, they won't be able to, as no commits will show for this branch. h3. Steps to Reproduce There are no steps to reproduce this, this issue rarely occurs in some repos h3. Workaround Users have reported that pushing another commit or a new branch to the repo, solves the issue. You can also contact Bitbucket Cloud Support ([https://support.atlassian.com/contact/#/]) to fix the issue for your repository. h3. Update (October 2021): We have found the race condition that was responsible for this issue. While we couldn't fully eliminate it in the short-term we were able to significantly reduce its probability. Additionally, we have implemented it in such a way that we can easily fine-tune the parameters of the fix based on the customer impact. Please let us know here if you continue to be impacted by this issue and in the meantime please refer to the Workaround section above to unblock your workflow. For a long-term solution we have recently kicked off a project to fix the issue fully, but this is a larger project and will take us some time to complete. h3. Update (June 2023): We have been actively monitoring this issue and we are happy to see that the issue has been impacting our customers at a much lower pace over the last several months. We attribute this improved trajectory to numerous architectural improvements we were able to put in place over the last while. The issue is still occassionally reported but it is unclear now whether it still shares the same root cause as its original counterpart. As a result, we have decided to close this original issue and start tracking the symptoms under a new BCLOUD ticket. This will allow us to more easily track the influx of customer reports and focus on the latest possible root cause of the issue. If you experience these symptoms please report them under the new BCLOUD ticket. |
New:
h3. Issue Summary
Sometimes recent commits that exist on the remote repository are not visible in the website, in the 'Commits' page of the repo. This impacts users' ability to open Pull requests: if a user wants to open a PR for an affected branch, they won't be able to, as no commits will show for this branch. h3. Steps to Reproduce There are no steps to reproduce this, this issue rarely occurs in some repos h3. Workaround Users have reported that pushing another commit or a new branch to the repo, solves the issue. You can also contact Bitbucket Cloud Support ([https://support.atlassian.com/contact/#/]) to fix the issue for your repository. h3. Update (October 2021): We have found the race condition that was responsible for this issue. While we couldn't fully eliminate it in the short-term we were able to significantly reduce its probability. Additionally, we have implemented it in such a way that we can easily fine-tune the parameters of the fix based on the customer impact. Please let us know here if you continue to be impacted by this issue and in the meantime please refer to the Workaround section above to unblock your workflow. For a long-term solution we have recently kicked off a project to fix the issue fully, but this is a larger project and will take us some time to complete. h3. Update (June 2023): We have been actively monitoring this issue and we are happy to see that the issue has been impacting our customers at a much lower pace over the last several months. We attribute this improved trajectory to numerous architectural improvements we were able to put in place over the last while. The issue is still occassionally reported but it is unclear now whether it still shares the same root cause as its original counterpart. As a result, we have decided to close this original issue and start tracking the symptoms under a new BCLOUD ticket. This will allow us to more easily track the influx of customer reports and focus on the latest possible root cause of the issue. If you experience these symptoms please report them under the new BCLOUD ticket. https://jira.atlassian.com/browse/BCLOUD-22728 |
| Resolution | New: Timed out [ 10 ] | |
| Status | Original: Long Term Backlog [ 12073 ] | New: Closed [ 6 ] |
| Link | New: This issue was split into BCLOUD-22728 [ BCLOUD-22728 ] |
| Description |
Original:
h3. Issue Summary
Sometimes recent commits that exist on the remote repository are not visible in the website, in the 'Commits' page of the repo. This impacts users' ability to open Pull requests: if a user wants to open a PR for an affected branch, they won't be able to, as no commits will show for this branch. h3. Steps to Reproduce There are no steps to reproduce this, this issue rarely occurs in some repos h3. Workaround Users have reported that pushing another commit or a new branch to the repo, solves the issue. You can also contact Bitbucket Cloud Support ([https://support.atlassian.com/contact/#/]) to fix the issue for your repository. h3. Update (October 2021): We have found the race condition that was responsible for this issue. While we couldn't fully eliminate it in the short-term we were able to significantly reduce its probability. Additionally, we have implemented it in such a way that we can easily fine-tune the parameters of the fix based on the customer impact. Please let us know here if you continue to be impacted by this issue and in the meantime please refer to the Workaround section above to unblock your workflow. For a long-term solution we have recently kicked off a project to fix the issue fully, but this is a larger project and will take us some time to complete. |
New:
h3. Issue Summary
Sometimes recent commits that exist on the remote repository are not visible in the website, in the 'Commits' page of the repo. This impacts users' ability to open Pull requests: if a user wants to open a PR for an affected branch, they won't be able to, as no commits will show for this branch. h3. Steps to Reproduce There are no steps to reproduce this, this issue rarely occurs in some repos h3. Workaround Users have reported that pushing another commit or a new branch to the repo, solves the issue. You can also contact Bitbucket Cloud Support ([https://support.atlassian.com/contact/#/]) to fix the issue for your repository. h3. Update (October 2021): We have found the race condition that was responsible for this issue. While we couldn't fully eliminate it in the short-term we were able to significantly reduce its probability. Additionally, we have implemented it in such a way that we can easily fine-tune the parameters of the fix based on the customer impact. Please let us know here if you continue to be impacted by this issue and in the meantime please refer to the Workaround section above to unblock your workflow. For a long-term solution we have recently kicked off a project to fix the issue fully, but this is a larger project and will take us some time to complete. h3. Update (June 2023): We have been actively monitoring this issue and we are happy to see that the issue has been impacting our customers at a much lower pace over the last several months. We attribute this improved trajectory to numerous architectural improvements we were able to put in place over the last while. The issue is still occassionally reported but it is unclear now whether it still shares the same root cause as its original counterpart. As a result, we have decided to close this original issue and start tracking the symptoms under a new BCLOUD ticket. This will allow us to more easily track the influx of customer reports and focus on the latest possible root cause of the issue. If you experience these symptoms please report them under the new BCLOUD ticket. |
| UIS | Original: 132177 | New: 132084 |
| UIS | Original: 132003 | New: 132177 |
| UIS | Original: 131533 | New: 132003 |
| UIS | Original: 113011 | New: 131533 |
We have been actively monitoring this issue and we are happy to see that the issue has been impacting our customers at a much lower pace over the last several months. We attribute this improved trajectory to numerous architectural improvements we were able to put in place over the last while. The issue is still occassionally reported but it is unclear now whether it still shares the same root cause as its original counterpart. As a result, we have decided to close this original issue and start tracking the symptoms under a new BCLOUD ticket. This will allow us to more easily track the influx of customer reports and focus on the latest possible root cause of the issue. If you experience these symptoms please report them under the new BCLOUD ticket.
https://jira.atlassian.com/browse/BCLOUD-22728