Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Files unreadable in new version, An error occurred

Henrik Gerdtsson November 24, 2022

We have a directory in one repo that after upgrade to Bitbucket version 8.4.1 is unreadable. A popup saying An error occurred.

image.png

There are nothing in the Bitbucket loggs when this occurres. There is an entry in the nginx log with https code 204.

The first thing I did was to clone the repository. Not a problem. Then I pushed it to a newly created repo on out test server running version 7.21.4. Here there are no problems with viewing the directories and files. So I created a new repo in a Sanbox project on our production server and pushed the repo. Same problem as in the original repo.

So its time to jump to a conclusion. Somthing has happende between 7.21.4 and 8.4.1 that makes our directory and files unreadable.

Next thing to try is to rename the directory. The original name was creone-http-time-sync. I changed that to creone-sync. Now it is possible to view the directory in Bitbucket. But all of the files containt http-time gives the above error. Removing the sting http-time from the filenames makes them readable.

So I added http-time to another directory in the repo. Once again I get the error when trying to open the directory in Bibtucket.

From these limited test I would say that Bibucket cannot handle the sting http-time in a directory or filename. Why would that be? Is there a configuration to change to allow the filenames? Anyone alse experienced this issue?

Br
Henrik

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events