[wp-trac] [WordPress Trac] #18767: Trac comments seem buggy

[WordPress Trac]

#18767: Trac comments seem buggy
--------------------------------+----------------------------
 Reporter:  azaozz              |       Owner:
     Type:  defect (bug)        |      Status:  new
 Priority:  highest omg bbq     |   Milestone:  WordPress.org
Component:  WordPress.org site  |     Version:
 Severity:  major               |  Resolution:
 Keywords:                      |
--------------------------------+----------------------------

Comment (by nacin):

 Okay. This is caused by the Trac commit ticket updater, and it is not two
 consecutive commit messages, but a commit message that references multiple
 tickets.

 Say you have ticket A with 30 comments, and ticket B with 45 comments. If
 you have a commit message that references both A and B, the next comment
 on ticket A will be 31, but ticket B will also be 31.

 It seems that sometimes, it is the second referenced ticket (so, B) that
 screws up, while in the case of ticket:21390#comment:48, it's the first
 ticket that is referenced that is screwed up. It also doesn't appear to be
 a newer/older ticket thing. If someone can find a pattern, do let me know.

 This appears to be the bug report upstream:
 http://trac.edgewall.org/ticket/10681. It's ultimately not very
 descriptive, which is why it likely hasn't gotten any attention. If we can
 gather enough information I'm happy to increase its profile upstream.

 The commit updater code is here:
 http://trac.edgewall.org/browser/trunk/tracopt/ticket/commit_updater.py.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/18767#comment:9>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software