Closed
Bug 566666
Opened 15 years ago
Closed 14 years ago
phx prod does not initially sync a newly created account
Categories
(Cloud Services Graveyard :: Server: Sync, defect)
Cloud Services Graveyard
Server: Sync
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: tchung, Assigned: telliott)
References
()
Details
(Whiteboard: [weave1.3])
When creating a new account and purposely entering in the wrong second recaptcha word, client says successful sign in, but initial syncing fails. However, you are still signed in, and force syncing twice will eventually be successful
1) install weave 1.3b5 and point to phx prod (i edited my etc/hosts)
2) create a new weave account on prod using setup wizard and enter in correct user/name/phrase
3) choose sync everything option
4) on the recaptcha page, enter in correct first word, but incorrect second word
5) first off, it succeeds. blah, think known. now sync
6) verify sync fails to login , and check activity log
Activity Log: http://pastebin.mozilla.org/725324
NOTE: this works against prod dev servers
Expected:
- despite incorrect recaptcha key, i should still sign in and sync intially
Actual:
- initial sync error
Flags: blocking-weave1.3?
Reporter | ||
Comment 1•15 years ago
|
||
http://pastebin.mozilla.org/725321
Here's the initial activity log immediately after account creation and first sync. the one in comment 1 is after i tried force re-syncing twice
Assignee | ||
Comment 2•15 years ago
|
||
My suspicion is that there's two issues here.
The account is created, which means you hit the right word for recaptcha to succeed. If it hadn't been, you wouldn't have been able to get a node.
I suspect that the fact that sync eventually worked it means that there was a replication delay that prevented your account from being recognized the first few times.
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Flags: blocking-weave1.3?
Resolution: --- → WORKSFORME
Updated•2 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•