Opened 4 years ago

Last modified 4 years ago

#61143 new defect

GitHub login: The username is case sensitive

Reported by: iefdev (Eric F) Owned by: admin@…
Priority: Normal Milestone:
Component: trac Version:
Keywords: Cc:
Port:

Description

I recently updated my GitHub name to all lowercase, and noticed I no longer have any tickets listed at: ​https://trac.macports.org/wiki/Tickets

Most member/login systems are usually non case sensitive on the username, and it would be great if that could apply to the login here as well.

There's no real panic here because I have the ones I've started listed in a local md file as well. But if it can't/won't be fixed - could someone run some manual update on the ticket db, and update my name? I'd appreciate that.

Change History (6)

comment:1 Changed 4 years ago by raimue (Rainer Müller)

Trac Query is indeed case-sensitive when matching the username. Upstream report: ​https://trac.edgewall.org/ticket/5720

comment:2 Changed 4 years ago by raimue (Rainer Müller)

I have updated the values for owner and reporter in the ticket database to the lower case version of your nick name. I hope the queries should now work again as expected.

I also purged the old version from the session list, but I still see both in the username completion. I think this might be cached, so it could disappear after a while. If not, I will have to look again where this data comes from.

comment:3 in reply to:  2 Changed 4 years ago by iefdev (Eric F)

Replying to raimue:

Trac Query is indeed case-sensitive when matching the username. Upstream report: ​https://trac.edgewall.org/ticket/5720

Ah, so they'll eventually fix that. I thought it perhaps was in the GitHub hook, or something like that.


Replying to raimue:

I have updated the values for owner and reporter in the ticket database to the lower case version of your nick name. I hope the queries should now work again as expected.

I also purged the old version from the session list, but I still see both in the username completion. I think this might be cached, so it could disappear after a while. If not, I will have to look again where this data comes from.

Thank you! so much for the update. 👍 I could see the tickets I had now.

I guess you can close this ticket, unless it should be kept for tracking their update.

comment:4 Changed 4 years ago by mf2k (Frank Schima)

Note that a "request" ticket type is only for requesting a new port.

comment:5 Changed 4 years ago by mf2k (Frank Schima)

Type: request → defect

comment:6 in reply to:  4 Changed 4 years ago by iefdev (Eric F)

Replying to mf2k:

Note that a "request" ticket type is only for requesting a new port.

Thanks. 👍 Yes, I was thinking about that, or if it was me “requesting“ a change.

Note: See TracTickets for help on using tickets.