squash not working for PR after upgrade

[Former user]

We recently upgraded to bitbucket 7.21.6 LTS and PR-Booster 2022.09.28 and when we tried to squash it spun and then exited but no action done? Any known issues with this combination or debugging?

[Julius Davies [bit-booster.com]]

The good news: Squash / Amend / Rebase verified to be working in that combination.

The bad news: IF the source branch is configured to disallow history rewrites, the Squash / Amend / Rebase will silently fail. We just published version v2022.12.06 to fix that!

If the branch was setup to disallow history rewrites, PR-Booster’s “Squash” would try to Squash and then silently fail. v2022.12.06 now provides a useful error message in this case! Our big refactor to implement Bitbucket 8.x compatibility accidentally broke the error reporting in these cases.

Can you try v2022.12.06 and let me know if that fixes this for your team?

[Kevin Lee]

Squashing... Failed.

Force-Push failed... Push failed: necessary object missing.
Pushed object AnyObjectId[46c8885573f84cfc3ec53fc8d6ce1a9e6eccc0f4] has not been found in Git repository.
This may happen in case Bitbucket Server resources (processes count, memory or disk space) are exhausted.
Check Bitbucket Server state and retry push.
Push failed: necessary object missing.
Pushed object AnyObjectId[46c8885573f84cfc3ec53fc8d6ce1a9e6eccc0f4] has not been found in Git repository.
This may happen in case Bitbucket Server resources (processes count, memory or disk space) are exhausted.
Check Bitbucket Server state and retry push.

Thanks for the new version. We just upgraded to v2022.12.06 and tried squash and got the above?

Any other debug we can try for finding AnyObjectId[46c8885573f84cfc3ec53fc8d6ce1a9e6eccc0f4]?

[Kevin Lee]

we are also seeing issues with cherry-pick after initial upgrade of Bitbucket and PR-Boost. Please advise today as this is blocking releases. Can you upgrade ticket to highest priority.

Cherry-picking... Failed.

PR-Booster-2022.09.28 / Git-2.31.1 / Bitbucket-7.21.6 / Linux-3.10.0-1160.49.1.el7.x86_64-amd64

Exit=1 /bin/git commit -m NMX-73208 - Updated Carry PCR on correct stream entity instance while creating and loading

(cherry picked from commit 35f176b45e6359132744e281ee167487b002a493) -- ssh://[e-mail]:7999/nmxgroup/nmx.git

[Kevin Lee]

We have user just get this message look similiar to other errors? Can you please investigate too.

‌

[Julius Davies [bit-booster.com]]

We just published v2022.12.08 which might fix these issue, but we’re not 100% certain of that.

Our v2022.12.08 fix is much better at supplying PR-Booster’s amend / squash logic with “alternate” repositories to include when looking for git objects - which is essential when working with pull-requests that span forks.

‌

‌

[Ismail Uwair]

One of our users reported “PR booster "rebase --autosquash" seems to not work any more in bitbucket. Anyone else experience this?” even after last update we are still facing the same issue. Furthermore the user reported that create PR on cherrypick is not working neither. Please provide us a solution soon, this started to happen after we updated Bitbucket to latest version (v8.6.1), we are using version 2022.12.08 of your plugin.

[Przemyslaw Kalucki]

We also have problem with "rebase --autosquash" in version 2023.01.18

[Julius Davies [bit-booster.com]]

@Ismail Isleem - the cherrypick problem has been fixed (see PR-Booster v2023.02.08).

The “rebase --autosquash” problem is a known issue that we will fix soon, but it’s quite a big fix.

[Julius Davies [bit-booster.com]]

Waiting to hear back from Kevin Lee if the recent versions (2022.12.* or newer) of PR-Booster fixed this issue.