Some comments get stuck on "Sending..."

[Moshe Goldyan]

Happened to my colleague and now happened to me.

In the end - it doesn't send the comment (even after a long wait).

We lost a lot of time...

[Patrik S · Accepted solution]

Hey @Moshe Goldyan ,

and welcome to the Community!

In order for us to assist you in investigating this issue, we'll need to gather a few more details: 

• Where exactly were you trying to add a comment? Was it in a pull request, in an issue on the Issue tracker, etc? 

• Are there any error messages being shown once the comment fails to be posted?

• Does the issue occur consistently in all repositories or just in a subset?

• Have you tried posting the comment with a different browser? If not could you try and let us know how it goes? 
• Last, could you try using your browser's incognito mode and attempt to reproduce the issue? The incognito mode will not use cached content and will also disable the browser extension, which may help us narrow down the issue.

With this information, we'll be able to get a better picture of the issue and verify what might be causing this behavior.

Let us know in case you have any questions.

Thank you, @Moshe Goldyan !

Patrik S

[Moshe Goldyan]

Hi Patrick

Thank you for quickly replying to my issue.

It's in a pull request.

No error messages (not on my PC nor on my colleague's). However, there is noticeable slowness (right from the start).

It occurs in a specific pull request which has a bit over 1K interactions (i.e. comments and replies to comments).

My colleague and I are from different physical locations and use different operating systems. I'm using Windows 10 with the latest Chrome but I don't think it's related to the browser.

I have tried using incognito - it's the same.

I also tried "Add Comment Now" (same effect) and sending even a single comment using "Start Review" but still the same - "Sending...".

Refreshing the page still shows "Sending...".

Closing the tab and opening a new tab (navigating to the pull request) - everything is gone.

Thank you very much

[Patrik S]

Hello @Moshe Goldyan ,

Thank you very much for providing additional context.

Since you mentioned the impact is limited to a single pull request, and that is a considerably large pull request, I suspect this might be playing a role in the slowness you're facing.

By default, the diff view settings will load all the files at one when you open the pull request page. However, depending on the size of the PR, this may cause slowness on your browser, and in such cases, it's possible to configure the PR to load files individually, as you open them.

You can change this option by navigating to the Pull Request > selecting the Files Changed tab > Click on the cog icon in the right side of the page > change the Load Files option to Individually

After saving the change, refresh the page and verify if files are being loaded individually now. If yes, you can then try adding a comment and check if it's successfully posted.

Let us know in case you have any questions.

Thank you, @Moshe Goldyan !

Patrik S

[Moshe Goldyan]

First of all, thank you @Patrik S for providing a solution.

I think that this painful issue probably happened to other users as well and can avoided in the first place - with Atlassian's help.

It's quite annoying spending precious time on commenting (especially when it's a large code review) and later on finding out everything was for nothing.

Then, I guess most users probably won't know how to tackle this situation and some (like me) will turn for help.

If this knowledge is known to Atlassian and if (for example) there's a known threshold issue when there are a large number of files / comments, then I think it'd be great if Bit Bucket will automatically load files individually and issue a clear warning.

Otherwise, more users will suffer from this situation...

What do you think @Patrik S ?

Thanks in advance for your help,

    - Moshe

[Patrik S]

Hello @Moshe Goldyan ,

I definitely understand your point and we actually have documentation that outlines viewing limits in Pull requests: 

• Limits for viewing content and diffs 

When the viewing limits are reached, the pull request should automatically switch to an individual file view, and a warning message should appear.

However, your pull request seems large due to the number of comments, not the diff itself, so it may be the case that the number of comments is not triggering the automatic change to individual file view.

Additionally, based on the previous comments on this thread, it seems this is affecting a single large pull request only in your repository. Having +1,000 comments on a pull request is quite unusual, and this might be why we haven't seen similar reports from other users. This volume of comments can significantly impact the performance and usability of the pull request interface and can also make it difficult to manage and review effectively.

If you're able to share more about the use case, it might help us understand the situation better and provide more tailored advice.

However, generally speaking, breaking down the pull request into smaller, more focused parts could make the review process smoother and more efficient. Each part can address a specific concern, such as a feature, bug fix, or other changes, which can help reviewers concentrate on one aspect at a time. Breaking down the pull request into smaller, more manageable pieces could help alleviate some of the issues.

Thank you, @Moshe Goldyan !

Patrik S