nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Are code suggestions broken in Bitbucket 7.4?

markgillespien

Developers have started complaining that the newly introduced suggestions feature doesn't work anymore, and everyone gets the following error when trying to use the suggestion.

"We can't apply this suggestion to the source branch. You'll need to make this change manually."

(which is less than helpful, it's a very wordy "something went wrong")

Accepted answers

All comments

Bryan Turner

@markgillespien

I'd recommend opening a support request for this. Our automated test suite for suggestions is all green, and we're unable to reproduce any issues with suggestions internally. If you've recently upgraded, that may be related. That sort of information is better exchanged on a support ticket, rather than here on Community. Once we resolve your issue we can update this question with any relevant details in case someone else happens to hit whatever issue you're hitting.

Best regards,
Bryan Turner
Atlassian Bitbucket

mark_gillespie

Sadly our SEN expired 2 weeks ago, and we aren't renewing,

I did try updating GIT to latest supported, and rebooting the server, but it's not helped.

Bryan Turner

I'm interested in helping, but realistically without logs and additional information about your instance there's not a lot I can do. If suggestions fail to apply in a way that shows that popup, there should be an error/stack trace in the logs on the server with more details about the failure.

Your title indicates you're on 7.4 now, but have you recently upgraded? If so, what version did you start out with? Something 6.x, perhaps? When this issue happens for developers, is it in pull requests that were open before the upgrade, or does it also happen in new pull requests created after? (Given 7.4 was only released recently, it seems like there must have been some upgrade involved.)

Unfortunately, here on this public issue isn't a great place to exchange details like this. If you want to ping me directly via email, I'm happy to see if I can get you sorted.

Best regards,
Bryan Turner
Atlassian Bitbucket

mark_gillespie

We track versions quite closely, as there are always nice additions (thanks!!), so we came from 7.3 (which did work to my knowledge).

I did run the system log inspector but it didn't come back with any errors, I will take a look the logs and see if I can see anything.

In my mind, there are two possible things that we did within the timeframe it started that could be causing this:

Upgrade to 7.4
Change Default Merge Strategy to Squash on Merge.

I don't think it's the later, as we have some other projects that have always been squash on merge, and they didn't have any trouble. The problem for us appears across all repos and projects.

Looking at the logs, I am seeing alot of these:

2020-08-11 09:37:51,235 INFO [drift:thread-4] c.a.s.i.p.c.d.DriftCommentUpdateProcessor 572:2495@11: Comment 78696 is already in the current diff (617864c71166d55793f43439443f5bebfb2f79bb, d2f70358852ac9a3574cf5cf0590d4a787375feb) and will not be drifted
2020-08-11 09:37:51,235 INFO [drift:thread-4] c.a.s.i.p.c.d.DriftCommentUpdateProcessor 572:2495@11: Comment 78698 is already in the current diff (617864c71166d55793f43439443f5bebfb2f79bb, d2f70358852ac9a3574cf5cf0590d4a787375feb) and will not be drifted
2020-08-11 09:37:51,235 INFO [drift:thread-4] c.a.s.i.p.c.d.DriftCommentUpdateProcessor 572:2495@11: Comment 78707 is already in the current diff (617864c71166d55793f43439443f5bebfb2f79bb, d2f70358852ac9a3574cf5cf0590d4a787375feb) and will not be drifted
2020-08-11 09:37:51,235 INFO [drift:thread-4] c.a.s.i.p.c.d.DriftCommentUpdateProcessor 572:2495@11: Comment 78703 is already in the current diff (617864c71166d55793f43439443f5bebfb2f79bb, d2f70358852ac9a3574cf5cf0590d4a787375feb) and will not be drifted
2020-08-11 09:37:51,235 INFO [drift:thread-4] c.a.s.i.p.c.d.DriftCommentUpdateProcessor 572:2495@11: Comment 78702 is already in the current diff (617864c71166d55793f43439443f5bebfb2f79bb, d2f70358852ac9a3574cf5cf0590d4a787375feb) and will not be drifted
2020-08-11 09:37:51,235 INFO [drift:thread-4] c.a.s.i.p.c.d.DriftCommentUpdateProcessor 572:2495@11: Comments have already been drifted (617864c71166d55793f43439443f5bebfb2f79bb, d2f70358852ac9a3574cf5cf0590d4a787375feb) when processing 1 drift request(s):

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

bitbucket

bitbucket-server