New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 667263 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Desync in cs.chromium.org indexation for chromium sources

Project Member Reported by a-...@yandex-team.ru, Nov 21 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 YaBrowser/16.11.0.1821 (beta) Yowser/2.5 Safari/537.36

Steps to reproduce the problem:
Encountered today minor desync in cs.chromium.org indexation.
Clicking on code references link for some variables navigates not to line where variable is defined for example, but to line that is several lines below the definition.

For example:
1. Open https://cs.chromium.org/chromium/src/components/search_engines/template_url_data.h?q=TemplateURLData&sq=package:chromium&l=83
which points to TemplateURLData structure definition.
2. click on last_modified field
3. Below the main window XRefs window opens with references to definitions and references to this field.
4. Click on link to definition of last_modified.

What is the expected behavior?
I expect that main window navigates to the line where last_modified field is defined.

What went wrong?
Main window navigates to  line 89 with content - // Number of times this TemplateURL has been explicitly used to load a URL.

Did this work before? N/A 

Chrome version: 54.0.2840.71  Channel: n/a
OS Version: OS X 10.11.6
Flash Version: Shockwave Flash 24.0 r0
 

Comment 1 by a...@chromium.org, Nov 21 2016

Components: Infra>Codesearch

Comment 2 by benhenry@google.com, Nov 23 2016

Cc: dsansome@chromium.org emso@chromium.org
Status: Untriaged (was: Unconfirmed)
Status: WontFix (was: Untriaged)
This could've been related to  issue 666799 , but that was fixed before you raised this one, so *shrug*.

It's hard to diagnose what happened afterwards, but we've got issue 667200 to add monitoring to the whole pipeline latency, which will include grok xref indexing.

Sign in to add a comment