Request to run garbage collector to remove read-only mode

[DottD]

Hi, all my repositories have been marked as read-only since I had one of them reaching almost 1GB. Now I reduced its size (actually removed the repo completely and recreated from scratch), but still cannot push to it; probably it is still marked as read-only. How can I overcome this? I read in other threads that requesting to run garbage collector may solve this issue.

Thanks in advance.

Filippo

[Robert Wen_Cprime_ · Accepted solution]

Hi @DottD ! Welcome to the Atlassian Community!

I've contacted Support about your GC request.

[Ben]

Hi @DottD 

I can see that you've deleted the ita** repository as it was 950mb in size (I've censored this as this is a public forum).

I've just restored the repository and executed a gc to reduce its size down to 250mb - and can confirm you are still within the 1GB limit. This restored repository has "-restore" appended to the end of the title, you can view it by clicking the Repositories tab on your workspace.

You'll need to perform the following:

1. Delete your local working copy of that repo from your local machine
2. Delete the blank repo you created by navigating to Repository Settings > Repository Details and click the Manage Repository dropdown in the top right, select Delete repository to delete the repo
3. Rename the restored repo to its original name by navigating to Repository Settings > Repository Details and change the repository name in the textbox, then click Save Changes
4. Perform a fresh clone of the reduced size restored repository and continue working

I hope this helps. Please let me know if any issues.

Cheers!

- Ben (Bitbucket Cloud Support)

[DottD]

Hi Ben,

thank you very much for your support.

I followed your suggestions, but I still get an authentication error message when I try to push to every repo (while I can clone them easily): "Unauthorized. fatal: Could not read from remote repository." Is something related to BitBucket repos configuration?

Bests

Filippo

[Ben]

Hi Filippo,

Are you using HTTPS or SSH?

Cheers!

- Ben (Bitbucket Cloud Support)

[DottD]

Hi Ben,

I am using SSH and I set up the keys in both the project and the repo.

Cheers

Filippo

[Ben]

Hi DottD, 

Can you please share the full error output for me when you attempt to push? Does it mention anywhere that your workspace is in read-only mode?

Cheers!

- Ben (Bitbucket Cloud Support)

[DottD]

Hi Ben,

no, it never mentioned the read-only mode; I got informed about it on this forum. You’ll find below the error message I get:

“Unauthorized

fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.”

Cheers

Filippo

[Ben]

Hi @DottD 

That error message is unrelated and refers to authentication issues. Can I get you to attempt to clone via HTTPS and let me know if the result is different?

Cheers!

- Ben (Bitbucket Cloud Support)

[DottD]

Hi Ben,

I tried with HTTPS but I get "Invalid Credentials" even when cloning the repo. I reset my password, but the problem remains. I really don't understand what's the problem here :(

Cheers

Filippo

[Ben]

Hi @DottD 

If you're receiving invalid credentials for HTTPS, pleas make use of an AppPassword for communicating to GIT via HTTPS.
We have documentation for usage of app passwords at the following link:
https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/#Create-an-app-password

Essentially, when connecting via HTTPS you will use your App Password alongside your username seperated with a ":" character.

Therefore if you are authenticating to GIT over HTTPS to push/pull you will need to update your remote URL's to include the App Password:

git remote set-url origin https://USERNAME:APP_PASSWORD@bitbucket.org/workspaceID/reposlug.git

I would suggest ensuring also that all stored passwords related to authentication over GIT are cleared from your machine (ie Credential Manager for Windows, Access Keychain for Mac or /etc/shadow folder for Linux).

Hope this helps.

Cheers!

- Ben (Bitbucket Cloud Support)