- From: Ryan Lane <rlane32@gmail.com>
- Date: Wed, 30 Jan 2013 17:14:38 -0800
- To: Scott Rowe <scottrowe@google.com>
- Cc: Doug Schepers <schepers@w3.org>, Julee <julee@adobe.com>, "public-webplatform@w3.org" <public-webplatform@w3.org>, Denis Ah-Kang <denis@w3.org>
- Message-ID: <CALKgCA2V3oq8cqQ85Caqupv3N0srpU341op8jYtrW+=3GHcCuA@mail.gmail.com>
Finished. If you had logged in with the "Remember my login on this browser" option in the past, then you'll still be logged in. You likely will be logged out otherwise. - Ryan On Wed, Jan 30, 2013 at 2:55 PM, Scott Rowe <scottrowe@google.com> wrote: > Thanks for clarifying. For those following along, that's 5:00 p.m. Pacific > Standard Time, 8:00 p.m. Eastern Standard Time, and lo and behold, 1:00 > a.m. Greenwich Mean Time (aka Universal Time Coordinate). > > Be sure you are not editing pages in the minutes immediately preceding > this time, and wait for Ryan to give the ALL CLEAR signal (with emphasis on > "Clear" - sorry, I couldn't resist). :) > > +Scott > > > > On Wed, Jan 30, 2013 at 2:47 PM, Ryan Lane <rlane32@gmail.com> wrote: > >> Ugh. Sorry. I did indeed mean 01:00 UTC tomorrow. I had used a google >> search for the current time in UTC and it's display is odd. Next time I'll >> use my Linux system. >> >> /me hangs his head in shame. >> >> >> On Wed, Jan 30, 2013 at 2:37 PM, Ryan Lane <rlane32@gmail.com> wrote: >> >>> I had meant 5 hours after I sent the email, which is at 20:00 UTC >>> >>> >>> On Wed, Jan 30, 2013 at 2:25 PM, Scott Rowe <scottrowe@google.com>wrote: >>> >>>> I think Ryan means he's going to make the changes at 01:00 UTC tomorrow >>>> - which would be five hours later than 20:00 UTC today. Is that right? >>>> +Scott >>>> >>>> >>>> >>>> On Wed, Jan 30, 2013 at 12:15 PM, Ryan Lane <rlane32@gmail.com> wrote: >>>> >>>>> Ok, then, I'll do it 5 hours from now (20:00 UTC) >>>>> >>>>> - Ryan >>>>> >>>>> >>>>> On Wed, Jan 30, 2013 at 11:46 AM, Doug Schepers <schepers@w3.org>wrote: >>>>> >>>>>> Hi, Ryan- >>>>>> >>>>>> My suggestion, unless someone on this list says boo, is to ask you to >>>>>> schedule it for later tonight, so we can see if it helps right away. >>>>>> >>>>>> Regards- >>>>>> -Doug >>>>>> >>>>>> >>>>>> On 1/30/13 2:34 PM, Ryan Lane wrote: >>>>>> >>>>>>> I just set up the new memcached support on test. I can also enable >>>>>>> this >>>>>>> for current docs, but it's going to log everyone out and clear all >>>>>>> parser cache when I do so. >>>>>>> >>>>>>> Do we want to schedule this, or shall I just do it? >>>>>>> >>>>>>> >>>>>>> On Wed, Jan 30, 2013 at 10:18 AM, Doug Schepers <schepers@w3.org >>>>>>> <mailto:schepers@w3.org>> wrote: >>>>>>> >>>>>>> Hi, Ryan- >>>>>>> >>>>>>> What steps would we need to do to try the memcache solution you >>>>>>> suggested, and when could we get that done? >>>>>>> >>>>>>> Regards- >>>>>>> -Doug >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 1/30/13 1:15 PM, Julee wrote: >>>>>>> >>>>>>> Hi, everyone: >>>>>>> >>>>>>> The session bug[1] is back. This means when folks edit a >>>>>>> page, >>>>>>> and then >>>>>>> click "save page" to submit the changes, they'll get the >>>>>>> following error: >>>>>>> >>>>>>> "/Sorry! We could not process your edit due to a loss >>>>>>> of >>>>>>> session >>>>>>> >>>>>>> data. Please try again. If it still does not work, try >>>>>>> logging >>>>>>> out and >>>>>>> logging back in."/ >>>>>>> >>>>>>> >>>>>>> Some other folks have mentioned experiencing different >>>>>>> errors. >>>>>>> If you >>>>>>> have any other problems with logging in, out, or staying >>>>>>> logged in, >>>>>>> would you kindly update the bug with the specific steps it >>>>>>> takes to >>>>>>> reproduce that error? >>>>>>> >>>>>>> Let's get this little guy nailed down! >>>>>>> >>>>>>> J >>>>>>> >>>>>>> [1] https://www.w3.org/Bugs/__**Public/show_bug.cgi?id=19914<https://www.w3.org/Bugs/__Public/show_bug.cgi?id=19914> >>>>>>> <https://www.w3.org/Bugs/**Public/show_bug.cgi?id=19914<https://www.w3.org/Bugs/Public/show_bug.cgi?id=19914> >>>>>>> > >>>>>>> >>>>>>> ---------------------------- >>>>>>> julee@adobe.com <mailto:julee@adobe.com> >>>>>>> @adobejulee >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >
Received on Thursday, 31 January 2013 01:15:26 UTC