On Jan 30, 2014, at 12:53 PM, Ryan Kelly <[email protected]> wrote:
> On 31/01/2014 4:38 AM, Chris Karlof wrote: >> Acknowledged and I can reproduce. Our patch to point to the prod token >> server didn't make it into nightly yesterday, so it's using the very old dev >> one. Nightly is currently getting 401s from this old dev server. I'll >> investigate. > > "old dev server" is right, it's so old that it didn't have the > corresponding server-side fix for this bug: > > https://bugzilla.mozilla.org/show_bug.cgi?id=957503 > > I've patched it but we really need to stop talking to this server, it's > not running the correct protocol version of either TS or Sync. > Coming tonight I hope: https://bugzilla.mozilla.org/show_bug.cgi?id=963251 -chris > > Ryan > > >> On Jan 30, 2014, at 9:13 AM, Edwin Wong <[email protected]> wrote: >> >>> That’s my understanding there’s a fix to make that a smoother flow [1] >>> It takes 3-8sec to sign in and everything just pops in. Well that was >>> yesterday when things were working. >>> >>> -e >>> >>> ------ >>> [1] https://bugzilla.mozilla.org/show_bug.cgi?id=965461 >>> >>> On Jan 30, 2014, at 9:09 AM, Tracy Walker <[email protected]> wrote: >>> >>>> >>>> But confirmed what you're seeing yesterday trybuild , working client, is >>>> no longer able to sign in. In fact tried them this moerning and each >>>> client connect to test account had been logged off. >>>> >>>> Question: Is log-out automatic on client shutdown, then client has to >>>> re-auth to FxA on startup? >>>> >>>> >>>> On 1/30/14, 11:04 AM, Edwin Wong wrote: >>>>> Thanks Tracy… You’re totally right - limit variables, isolate and >>>>> validate changes. >>>>> >>>>> From what we know: Authentication servers did not change, Fx binary >>>>> didn’t change either. I do know: >>>>> * dev old sync/token - issues >>>>> * prod and stage token server - ssl cert issues >>>>> >>>>> -e >>>>> >>>>> >>>>> >>>>> >>>>> On Jan 30, 2014, at 7:49 AM, Tracy Walker <[email protected]> wrote: >>>>> >>>>>> Edwin, >>>>>> >>>>>> Experience has shown that testing unknown client with unknown servers >>>>>> makes it difficult to track what broke where. Thus, in the past, we >>>>>> kept client trains and server trains separate. I know we don't have that >>>>>> luxury at this point in time with FxA featuring Sync. What I suggest >>>>>> is, if you want to test the changes on server side that you use >>>>>> client(s) of a known state, buggy or not, but known. For testing the >>>>>> client use known servers (prod). Only test both in unknown state when >>>>>> patches had to land in both realms to fix an issue. >>>>>> >>>>>> my .02 :-) >>>>>> >>>>>> Tracy >>>>>> >>>>>> >>>>>> On 1/30/14, 9:19 AM, Edwin Wong wrote: >>>>>>> I think we’re currently blocked by this since 2-3pm yesterday - any >>>>>>> updates? >>>>>>> >>>>>>> Unable to sync data when signing in with fxa starting at 2:30 PST (edit) >>>>>>> https://bugzilla.mozilla.org/show_bug.cgi?id=965618 >>>>>>> >>>>>>> 0. get team build from here: >>>>>>> http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/fx-team-macosx64/1390969090/ >>>>>>> >>>>>>> 1. enabled fxA then enter in form and choose 1960s with: >>>>>>> user: >>>>>>> [email protected] >>>>>>> pw:mozdemomozdemo >>>>>>> * possible authentication issue >>>>>>> >>>>>>> actual: the remote hosted page says 'manage' but all other UI >>>>>>> (menu/prefs) shows you're not signed in. >>>>>>> >>>>>>> expected: you should be signed in in the menu and prefs. >>>>>>> >>>>>>> >>>>>>> ———— >>>>>>> not sure what's going on but I get the same issue when i set the >>>>>>> following token pref: >>>>>>> >>>>>>> http://auth.oldsync.dev.lcip.org/1.0/sync/1.1 >>>>>>> https://token-stage2.stage.mozaws.net/1.0/sync/1.5 >>>>>>> https://token.services.mozilla.com/1.0/sync/1.5 >>>>>>> >>>>>>> this is a blocker for any desktop fx testing >>>> >>> >> >
_______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
