Issue #6830 resolved

Commits are visible in "Recent Activity" but shows 404 when clicked

RDS
created an issue

I just pushed my commits to bitbucket. I can see those commits in my "Recent Activities" and also in "Dashboard" But when I click on it. Its shows 404.

Also "Commits" tab does not show those (recently pushed) commits.

Feel free to access my account to verify this.

Comments (17)

  1. Zach Davis staff

    Hi there,

    I'm seeing a recent push of two commits on the Overview tab for that repository; both of those commits on the Commits tab; and the link provided above (as well as the link from the Recent Activity) work properly. Are you still seeing this problem?

    Thanks, Zach

  2. RDS reporter

    It would be great if you check (validate) this bug, because if I do any "git push origin master", you wont be able to check it. 404 will be resolved.

    And I need to make do git push origin master to move my latest code to server.

    I would request you to check this bug today. Thank you.

  3. Zach Davis staff

    I can see the 404 now, but I can't see any cause for it, unless your repository is in a strange state (perhaps from rebasing?). We haven't seen any other reports of this, so it seems to be specific to your repository.

    Also, since you only appear to have one branch ("master") in your repo, I'm unclear as to how git push would do anything different than git push origin master. The latter should do the same as the former (assuming you're on the master branch), it's just more explicit.

  4. RDS reporter

    That's what I am saying, It seems like a bug to me. You should investigate and solve it.

    I did not rebase it, I wanted to but I couldn't, because I did not know how to do it. That's why I deleted the repository C4T and created it again. Also I am using Zend Studio and IDE, and using integrated git. I dont know why but instead of creating "origin" it created "original" Now I push using "git push original master"

    That's all information I have for you, You can have a look at my account history to pin point the bug.

  5. Myles Noton

    I also see the same 404 issue with one of my repos after pushing to "original" with Zend Studo's integrated Git client, and see the commit in the recent activity.

  6. Nicolas Venegas

    Hi

    This looks like it may be due to a configuration problem when using Zend.

    If you're familiar with the file structure of a git repository (the files in the .git directory), the branches of a repository come from the .git/refs/heads/ directory, and each file will typically point to a commit hash.

    Looking at the rahulprasad/c4t repository on our servers, I see that the master branch (refs/heads/master) points to 66b309e60c6b5d99801eefcb267172fa82ff56c8 whereas the file refs/for/refs/heads/master points to 3bf9665947ec6c0d951ed25bdc66d79ecb7155c6, which is the commit in question in this issue that 404s.

    So the commit 3bf9665 exists in the repository on our servers, but since it isn't reachable by a valid branch, we 404 on it (we do this because git repositories can keep around 'garbage' commits that are no longer reachable).

    Would you mind checking the .git/config file in your local repository to see how the original remote is set up?

    Cheers

    Nicolas

  7. RDS reporter

    Here is the output of my local/.git/config file

    [core]
        repositoryformatversion = 0
        filemode = true
        logallrefupdates = true
    [remote "original"]
        url = https://rahulprasad@bitbucket.org/rahulprasad/c4t.git
        fetch = +refs/heads/*:refs/remotes/original/*
        pushurl = https://rahulprasad@bitbucket.org/rahulprasad/c4t.git
        push = HEAD:refs/for/refs/heads/master
    [branch "master"]
        remote = original
        merge = refs/heads/master
    [gerrit]
        createchangeid = true
    
  8. Log in to comment