hosna
(hosna)
2019 年12 月 11 日 20:40
4
我不知道这是否相关。我通过 API 注册用户。我从用户处获取用户名,并通过 API 检查该用户名是否存在;如果存在,则选择 Discourse 建议的替代方案。然而,很多时候 Discourse 建议的用户名实际上是一个真实存在的用户名,但该用户的账户似乎已损坏。我的意思是,当我尝试查看其个人资料时,会收到一个“未找到”的错误页面。
顺便提一下,我已在以下链接报告了这些损坏的用户账户:
I just changed the username of a person xxx on their demand. they wanted to take an inactive username yyy. so first I changed the inactive username yyy to somthing else like yyy1 and then changed that person username from xxx to yyy.
at this point, first, the user couldnt post anything and I saw the following error in the logs:
Job exception: PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "index_users_on_username_lower" DETAIL: Key (username_lower)=(mina) already ex…