[Bug 47848] Renaming a user apparently doesn't reset the cached username associated with that user object

2014-03-20 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=47848 Andre Klapper aklap...@wikimedia.org changed: What|Removed |Added Priority|High|Normal -- You

[Bug 47848] Renaming a user apparently doesn't reset the cached username associated with that user object

2013-10-18 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=47848 --- Comment #5 from Andre Klapper aklap...@wikimedia.org --- Is this still an issue in times of SUL? Should this still be high priority? -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the

[Bug 47848] Renaming a user apparently doesn't reset the cached username associated with that user object

2013-04-30 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=47848 Andre Klapper aklap...@wikimedia.org changed: What|Removed |Added Priority|Unprioritized |High ---

[Bug 47848] Renaming a user apparently doesn't reset the cached username associated with that user object

2013-04-29 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=47848 Ryan Kaldari rkald...@wikimedia.org changed: What|Removed |Added CC||s...@reedyboy.net

[Bug 47848] Renaming a user apparently doesn't reset the cached username associated with that user object

2013-04-29 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=47848 --- Comment #2 from Gerrit Notification Bot gerritad...@wikimedia.org --- Related URL: https://gerrit.wikimedia.org/r/61491 (Gerrit Change I52f81aacf3d4f8ec7afa058159d07a74c0d9ff9e) -- You are receiving this mail because: You are the assignee

[Bug 47848] Renaming a user apparently doesn't reset the cached username associated with that user object

2013-04-29 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=47848 --- Comment #3 from Ryan Kaldari rkald...@wikimedia.org --- It looks like Renameuser does actually clear the memcached data, but perhaps there is a concurrency issue with the user cache being regenerated before the username change is replicated