An error has occurred A problem was encountered processing your request. The tracker maintainers have been notified of the problem.
evandrocoan opened this issue · 11 comments
I had and account a year ago, but now I tried to login it said to me the user was non-existent. Then I created a new account, and when I hit the confirmation button on my email it opened this page:
Did you get informed of the problem?
How can I report bugs?
It seems that you're able to create the account in bpo now, so you'll have to actually create the unittest bug there. Sorry for the trouble.
However, this is the appropriate place to report issues with the account creation itself.
I am trying to log in, but it keeps telling me:
- broken form: multiple @action values submitted
I managed to login by directly accessing the page with this link:
Before I was accessing the confirmation link:
And trying to login from that page:
Then, it was saying this bug:
Perhaps @ewdurbin or @ezio-melotti can take a look. I don't have access to the logs.
The issue appears to be a database constraint:
IntegrityError: duplicate key value violates unique constraint "_user_key_retired_idx" DETAIL: Key (__retired__, _username)=(0, addons_zz) already exists.
So it appears that multiple registration attempts with the same username addons_zz were initiated, and at least one was completed.
So that at least explains the first issue, combined with the other referenced issue it appears that between the two email addresses @evandrocoan tried to use, one of them was successful in creating a n account.
When the user clicked the confirmation link for a second time, the OTK tried to create an account with the same user name, and obliterated the one time use key. @evandrocoan do you have an error message or screenshot for what that looked like?
I'm able to reproduce the multiple @action values submitted error by going to https://bugs.python.org/?@action=foo, receiving an No such action "foo" error, then trying to log in.
Will look into if there's away to strip the outer @action from the POST used to log in, but I'm not sure it will be that simple.
@evandrocoan do you have an error message or screenshot for what that looked like?
I have posted on this thread all screenshots I got. I think what you want now, would be this screenshot:
For the double @action issue, See:
'''
changeset: 5294:3e740c65510e
user: John Rouillard rouilj@ieee.org
date: Thu Sep 28 16:48:52 2017 -0400
files: website/issues/html/page.html
description:
Fix double @action failure when you do a full text search and then
attempt to show an issue. The original action="#" included the searches
@action in the url and the show issue included another @action=show.
'''
in the upstream repo: https://sourceforge.net/p/roundup/code/ci/3e740c65510e
Ran into this issue (logged in with github once, but my email wasn't public, made it public and tried again, got this error).
Is there something I can do about it? Maybe like a manual step?
We now migrated to GitHub, so this can be closed.