On 15/04/2016 12:26, Mark Hammond wrote: > On 15/04/2016 3:26 AM, Ryan Feeley wrote: >> From another device, click the reset link and create a new password >> From original browser, I tried to log in but got “attempt limit >> exceeded”. Maybe you will get this too. >> I was also unable to sign in to manage account/change avatar (attempt >> limit exceeded) > > That sounds like a server issue, and I agree it's strange and > potentially quite confusing to the user.
I'm hopeful that these are resolved as of today's redeploy. Longer term, we need to distinguish between "you personally tried too many times" and "we're blocking your IP because we think you're a bot" and a server-side issue is definitely to right place to follow up on that. Ryan >> ACTUAL RESULTS (AR) >> I was able to change the device name locally >> EXPECTED RESULTS (ER) >> I should not be able to change the device name locally > > hrm - I guess this is a client issue, but I'm not sure it should be > treated as a bug. Changing the client name in about:preferences#sync > just sets a preference - so it can be changed even when the device is > off-line. On the next Sync we'll update the servers (both FxA and the > Sync clients collection) with the new name. > > I'd agree it is a problem if the change in the name doesn't end up > having any effect - but I suspect it will end up doing the right thing > when we can finally Sync again. I'm open to discussing how to do this > better, but I'm not yet convinced we should. I guess it would be > possible to detect that we failed to update the server on-the-fly and > show a lightbox or similar with messaging to the effect of "we couldn't > update the name now, but we will do it later" if you think that's > worthwhile. If so, please open a bug an attach a rough mock-up. > >> AR: Sync preferences did not indicate I was disconnected >> ER: Sync preferences should enter verification required state > > Yeah, this sucks, but is being tackled in bug 1262272 - the client-side > portion of this is ready to land, but the server part of this hasn't > been opened yet (it was only today that I learned there *was* a server > component of that - I was assuming magic happened :) > > I asked Kit to link to the server side PR/bug in bug 1262272. > >> AR: Another device (desktop release) in the constellation was able to >> update my display name >> ER: Another device should have no way to do that as I’m not connected > > Huh, I agree that's weird, but that appears to also be a server issue > (the change of your display name is done directly on the web - the > client's not involved at all) > >> AR: I can perform a manual sync, and the Last Sync time updates, >> though the other device does not see my new tabs >> ER: I should not be provided with feedback about something that is >> happening when it isn't > > Yeah, this is a side-effect of how credential changes are handled by > Sync, but once bug 1262272 is complete we shouldn't be able to hit this > - so I'd say there's no need to action this directly. > > The above isn't particularly helpful - but hopefully it's a tiny bit > helpful :) > > Mark. > _______________________________________________ > Sync-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/sync-dev _______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
