Opened 13 years ago
Closed 12 years ago
#18767 closed defect (bug) (fixed)
Trac comments seem buggy
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | WordPress.org | Priority: | highest omg bbq |
Severity: | major | Version: | |
Component: | WordPress.org Site | Keywords: | |
Focuses: | Cc: |
Description
Seems we have two "comment:22" http://core.trac.wordpress.org/ticket/18314#comment:22 on #18314. Tried to edit the second one but the edited content went into the first :)
Change History (19)
#2
@
13 years ago
Yes, looks like something went wrong when the commit message was added to the comments.
#3
@
13 years ago
More duplicate comment IDs: http://core.trac.wordpress.org/ticket/18785#comment:77
#5
@
13 years ago
- Priority changed from normal to highest omg bbq
This problem is still in the wild, can it be fixed? Mostly happens in tickets with many comments.
:)
#7
@
12 years ago
I think I've only seen this caused by an automatic commit message. Does that sound about right? If so, I can dig into that area of the code.
#8
@
12 years ago
Two consecutive commit messages maybe? http://core.trac.wordpress.org/ticket/21390#comment:48
#9
@
12 years ago
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.
#10
@
12 years ago
More:
- http://core.trac.wordpress.org/ticket/21309#comment:39
- http://core.trac.wordpress.org/ticket/20103#comment:34
- http://core.trac.wordpress.org/ticket/20103#comment:9 (second)
- http://core.trac.wordpress.org/ticket/20103#comment:5 (third)
- http://core.trac.wordpress.org/ticket/20103#comment:7 (third)
- http://core.trac.wordpress.org/ticket/20103#comment:25 (second)
- http://core.trac.wordpress.org/ticket/20103#comment:37
- http://core.trac.wordpress.org/ticket/20103#comment:34 (second)
#11
follow-up:
↓ 17
@
12 years ago
On a related note, "# was marked as a duplicate" message is sometimes posted twice:
#12
@
12 years ago
Yes, the first time, I inserted the ticket number in the comment field and I got an error and the comment was only posted on the other ticket.
#13
@
12 years ago
Yeah, I used something added in a later version of Python than this server runs, for a particular branch of code. I'll get it fixed.
#14
follow-up:
↓ 15
@
12 years ago
Some recent comments and tickets don't show up in wp-trac mailing list:
https://irclogs.wordpress.org/chanlog.php?channel=wordpress-ui&day=2012-10-16&sort=asc#m64458
#15
in reply to:
↑ 14
@
12 years ago
Replying to SergeyBiryukov:
Some recent comments and tickets don't show up in wp-trac mailing list:
https://irclogs.wordpress.org/chanlog.php?channel=wordpress-ui&day=2012-10-16&sort=asc#m64458
Unrelated, and fixed: http://make.wordpress.org/core/2012/10/17/trac-email-issues-are-fixed/
#16
@
12 years ago
This might be fixed with an update to Trac 0.12.4. See http://trac.edgewall.org/ticket/10881. I guess we'll find out.
#17
in reply to:
↑ 11
@
12 years ago
Replying to SergeyBiryukov:
"# was marked as a duplicate" message is sometimes posted twice
In my case, that happened when I linked a comment on the original ticket rather than the ticket itself in the comment field when closing a duplicate ticket. I got an error, as mentioned in comment:12.
Looks like it got to 23 and reverted back to 13 with a commit from you, then proceeded to count from there.
No idea what's going on here, but I can ask barry for a database snapshot if necessary.
This would be a bug in Trac, or probably more likely, a glitch with the database. We don't have any modifications affecting this.
Leaving this open as we can manually renumber them in the DB.