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; } } }

Having trouble showing file history

jknopp

Using the BB web interface, when I'm in the source view for a single file, the Commit History dropdown never populates, and if I select History from the first dropdown, it eventually times out with the error message "Having trouble showing file history".

This has been the case for months, most of the time (occasionally it works).

I know there'a bug with commit history when there are non-ascii characters in the path or filename, but that's not the case here.

The history comes up fine if I use command line git in a checked out copy.

Anyone else run into this?

Accepted answers

Patrik S

Hey @jknopp ,

and welcome to the Community!

I wasn't able to reproduce this behavior on my end with multiple repositories, so I'd like to ask you to perform a few tests:

Make sure to use one of the bitbucket supported browsers
Try loading the page in your browser's incognito mode, so we rule any any possible cache issue
Disable any browser extensions you may have and tests if the issue persists.

Additionally, is this issue happening for all users on your repository, or only for you?

All comments

Patrik S

Hey @jknopp ,

and welcome to the Community!

I wasn't able to reproduce this behavior on my end with multiple repositories, so I'd like to ask you to perform a few tests:

Make sure to use one of the bitbucket supported browsers
Try loading the page in your browser's incognito mode, so we rule any any possible cache issue
Disable any browser extensions you may have and tests if the issue persists.

Additionally, is this issue happening for all users on your repository, or only for you?

jknopp

Thanks for the response.

Of course it is working now. I have noticed it being a bit inconsistent before though, so not entirely surprising. I'll try your ignognito/extension steps next time I come across the issue.

Browser is up to date chrome so shouldn't be an issue there.

jknopp

Managed to catch it again. Seems the AJAX API is responding with a 500 (quite quickly in this case, so not identical to but perhaps related to https://jira.atlassian.com/browse/BSERV-13135 )
The URL (sanitized) is:
https://bitbucket.org/!api/2.0/repositories/<workspace>/website/filehistory/<fileid>/<path/filename)?pagelen=10&renames=false&fields=%2Bvalues.commit.message%2C%2Bvalues.commit.rendered.message%2C%2Bvalues.commit.author.%2A%2C%2Bvalues.commit.date

Probably related, also getting a 500 from:
https://bitbucket.org/!api/internal/repositories/<workspace>/website/srcdir-with-metadata/<fileid>/<path>

Not to mention a couple 404s in the user prefs API but seems unrelated.

Patrik S

Hello @jknopp ,

Sorry to hear you are facing this issue again.

Usually a server error (HTTP status code 500) is followed by an error code so we can search for it on our end.

When you inspect those failed API requests, do you see any error code either in the body of the response message or in the response headers (look for a header with "sentry" in its name)?

Welcome!

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

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud