Just made a commit and this is 3 minutes later still not visible in https://drupal.org/user/[uid]/track/code

Comments

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

Wrong link?

eliza411’s picture

eliza411 commented
Status: Active » Closed (cannot reproduce)

Without the commit hash, I can't be positive that the commit finally showed up, but I am seeing commits at https://drupal.org/user/85918/track/code since this was posted.

If the particular commit in question didn't appear, please re-open. Meanwhile, I'm consolidating issues with the commit logs for investigation.

eliza411’s picture

eliza411 commented
Issue tags: +git
jonathan1055’s picture

jonathan1055 commented
Title: "Your commits" does show latest commits » "Your commits" does not show latest commits

Fixed the title

hass’s picture

hass commented
Issue summary: View changes
Status: Closed (cannot reproduce) » Active

Have you changed anything? If not this still exists. My fealing is that it is cached up to 6h.

You must open the page, make a commit, reload don't show latest commit. Maybe you need to repeat this.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

@hass You need to clarify which project is missing commits, and the actual link to the page you're trying to use, because your original report does not contain a valid link.

hass’s picture

hass commented

This is my commit list, like yours. The link is correct. The list was not updated several hours after I made 6 commits to realname. After several hours the list was updated and showed all commits. This is a caching bug.

eliza411’s picture

eliza411 commented
Status: Active » Closed (cannot reproduce)

I'm not at all sure that we're seeing a caching problem.

There have been some intermittent issues with the workers that parse commit logs. Once the jobs are restarted, commits typically get parsed and appear.

Others reporting a similar problem have been helpful by providing the hash of the missing commit/s and actual links to where we should be seeing the commit. When they do that, we can troubleshoot more effectively. Without that information our time is wasted trying to reproduce issues based on inadequate data and/or the issue ends up being ignored and cluttering the queue.

I *can* make a commit, push it, and see the results immediately, so I'm inclined to suspect this was the by-product of the dead workers.

hass’s picture

hass commented
Status: Closed (cannot reproduce) » Active

What is so difficult here? I committed a bunch of patches. The first was shown immediatly and all followups not. What are you looking for from me several days after the issue disapeared 6h after the commits? What are you expecting from the commit messages? I can share them.

https://drupal.org/node/266280/commits, all november 2.

eliza411’s picture

eliza411 commented
Status: Active » Fixed

There is no evidence the problem you experienced is related to caching.
There *is* reason to believe that restarting log-parsing workers led to the resolution.
If I understand you correctly, the specific problem you reported - 3 missing commits - is resolved. I cannot be sure since I still don't know which specific commits weren't showing.

Marking this Fixed.

hass’s picture

hass commented

Again, the first commit in 2. november was shown and all 8 others not. What can you not see?

I don't know what the reason is behind, but it was broken and if something was broken without getting a fix it will be broken again. Why are you closing the case again without implementing a fix?

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

@hass You keep failing to understand that in order to help investigate this, you need to link to the specific missing commits on drupalcode.org that you do not see on your user page on Drupal.org. We have asked several times and you refuse to do so.

hass’s picture

hass commented

I told you several times that the issue was on 2. november. Today we have the 5. november and i have not made any further commits.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

Saying the issue was on 2 november does not mean the same thing as 'please paste a link to a specific commit on drupalcode.org from 2 november that you don't see on your commit page on drupal.org'.

One of those statements has the necessary information for others to help. One does not.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.