#4935 svn code browser showing inconsistent data [ss542]

v1.0.0
closed
nobody
General
nobody
2015-08-20
2012-09-13
Chris Tsai
No

[forge:site-support:#542]

In SF1, the SCM code viewer (viewvc) showed me the rev, age, and log message for the last commit made in the tree under that directory. So you could easily explore down the tree to find the last commit, for example.

In SF2, I cannot figure out what the new Subversion code browser is showing me for directories. It shows a date and commit info (rev and log message), but it is not the most recent in the tree under that. And it seems to change from time to time (without any commits). Yesterday I was seeing almost-newest commit info. Today I seem to be seeing the very first commit under that tree.

See also [allura:tickets:#4728], [forge:site-support:#228] and [allura:tickets:#4754]. If I'm reading it right, you had a similar problem with Mercurial (all_commit_ids), which was fixed, perhaps only for that SCM system?

For example, rev 1407 of their repo includes /branches/Rel6/phplot/phplot.php but viewing the directory that contains it in the code browser, it currently shows rev 1396. Screenshot attached.

1 Attachments

Related

Tickets: #4728
Tickets: #4754
Tickets: #5514

Discussion

  • Chris Tsai - 2012-09-21

    As per their latest comment the saga-gis project is also affected.

     
  • Dave Brondsema

    Dave Brondsema - 2012-09-21
    • milestone: limbo --> forge-oct-05
     
  • Dave Brondsema

    Dave Brondsema - 2012-09-21
    • size: --> 1
     
  • Dave Brondsema

    Dave Brondsema - 2012-11-02
    • Milestone: forge-nov-16 --> forge-nov-30
     
  • Dave Brondsema

    Dave Brondsema - 2012-11-16
    • size: 1 --> 0
     
  • Dave Brondsema

    Dave Brondsema - 2012-11-16

    [#4691] is probably the root cause of this.

     

    Related

    Tickets: #4691

  • Dave Brondsema

    Dave Brondsema - 2012-11-16
    • milestone: forge-nov-30 --> forge-backlog
     
  • Chris Tsai - 2013-01-10
    • labels: support, p3 --> support, p2
     
  • Chris Tsai - 2013-01-10

    Bumping to p2 due to volume of reports.

     
  • Dave Brondsema

    Dave Brondsema - 2013-02-19

    I believe this is fixed for new commits going forward, but existing commit data hasn't been reprocessed yet.

     
  • Chris Tsai - 2013-11-20
    • status: open --> closed
     

Log in to post a comment.