Since this morning, I've been unable to see the differences in the files when I view a pull request or a commit. It indicates to me "The diff for this file is empty."
The "Whitespace changes" parameter is checked, and I've disabled all extensions installed on Chrome.
The files indeed contain modifications.
Hello @William Lemieux ,
thank you for reaching out to the community.
Could you please confirm if when running the diff locally using the following command you get any output for those files?
git diff PR_destination_branch...PR_source_branch
This is the diff that is calculated in the UI when opening a pull request, so I'm interested to see if those files are listed with any change if executing the same command locally.
Thank you, @William Lemieux !
Patrik S
I confirm that the git diff command returns me all the diffs as bitbucket is supposed to.
Thank you for your help @Patrik S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Patrik S I confirm I can see the changes locally using the provided command. I can also see the diff when clicking on "View raw commit"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I noticed, in my case, that the problem seems to be present when the files names contains spaces OR files are present in a folder that contains spaces in the name
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @William Lemieux ,
Thank you for sharing additional details.
I can see you have an active bitbucket subscription in your workspace, so I will be raising an internal support ticket for this issue as we would like to take a look at the affected PR.
You should be receiving an email with the ticket link soon. In case you don't receive it, please let me know and I can share it with you here.
If you could respond to the ticket with the affected PR, this will definitely help speed up the investigation.
Hey @remi_ferland ,
I see you also have a workspace with an active subscription, so I will be raising a support ticket for you as well, so we can also investigate the issue you reported, as it may be caused by a different factor.
Thank you, folks!
Patrik S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Patrik S I'm facing the same issue. In my case, I can't see the diff of the the files which contains Japanese characters in its file path.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello all,
Our development team has already deployed a fix for the issue where some files were not correctly showing the diffs of pull requests/branches.
Could you please confirm if you are able to see the diffs now?
Thank you!
Patrik S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Patrik S I have just confirmed the fix. Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same problem on our end. Works in some repo and not in others.
Tried:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.