Opened 11 years ago

Closed 11 years ago

#20676 closed Bug (fixed)

Wrong users highlighted as core devs in trac

Reported by: Alex Couper Owned by: Baptiste Mispelon
Component: *.djangoproject.com Version: 1.5
Severity: Normal Keywords:
Cc: bmispelon@… Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

I assigned a ticket to myself anonymously and was given Core status:

https://code.djangoproject.com/ticket/20649#comment:4

I've now reassigned it to a registered version of me and all is well.

Change History (5)

comment:1 by Baptiste Mispelon, 11 years ago

Cc: bmispelon@… added
Owner: changed from nobody to Baptiste Mispelon
Status: newassigned
Summary: Trac gave Core dev status to Anon userWrong users highlighted as core devs in trac
Triage Stage: UnreviewedAccepted

The highlighting of core developers is done client-side with javascript.

As it turns out, the regular expression used to detect usernames stops at whitespace so your username ends up being Alex, a username belonging to Alex Gaynor who is indeed a core developer.

I'll look into this and see if the regex can be fixed or if we need to change something in trac.

Thanks.

comment:2 by Aymeric Augustin, 11 years ago

Computer.

:D

comment:3 by Baptiste Mispelon, 11 years ago

Has patch: set

After digging a bit deeper into this issue, I'm starting to think the only sane fix would be to make everone named Alex a core developer...

The problem we have is that trac sometimes likes to use the full name of a user instead of his/her username when displaying a comment.
This means that we can't check reliably whether a user is a core dev or not.

I "improved" the username-extracting code to reject everything containing an "@" character.
This won't fix the core issue, but it should at least get rid of the false positives.

I hope you enjoyed your "core dev" highlight while it lasted ;)

https://github.com/django/code.djangoproject.com/pull/7

comment:4 by Aymeric Augustin, 11 years ago

I applied the patch and I confirmed it fixes the issue.

comment:5 by Aymeric Augustin, 11 years ago

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.
Back to Top