*Theme: Coming to the end of train-71* I'll have to send the video next week, it's not yet available in vreplay.
Highlights: - We have had a long-standing issue with our cache busting URLs - the cache busting portion of the URL is an MD5 digest of the contents of the file. jrgm found the actual MD5 digest and the digest reported in the filenames did not match. Not only that, but the SRI values being used for some CSS files was not the actual SRI value. Since SRI hash mismatches prevent a resource from loading, this caused big issues. We tracked down the problem and fixed it [1]. We were calculating the MD5 and SRI values too early in the build process for all resources that themselves referred to other static resources. Train 70.2 is on its way with this fix. - Signin confirmation has been released to prod for a couple of months now. Vijay has updated the feature document with the conclusion and next steps [2]. TL;DR - the feature provides additional security for user's accounts, at the cost of increased signin friction. Next step is to increase the signin success rate by reducing the number of *legitimate* users who must go through the flow. - Train-71 strings were cut already (thanks Vlad!), Train-71 will be cut early next week. - State information is being added to location information in emails [3] - jrgm just approved a bunch of new locales [4] - Astorian (ast), Bengali-Bangladesh (bn-BD), Spanish-Spain (es-ES), Spanish-Mexico (es-MX), Indonesian (id), Georgian (ka), Kabyle (kab), Latvian (lv), Norwegian-Norway (nn-NO), Telugu (te) - Signin unblock is coming along massively. Sean McArthur has the server components in review, I have just opened several front-end and client PRs for review. I'm putting up a box now to test - if Ansible doesn't stop randomly it should be ready on [5] in about an hour. If Ansible does stop, I'll fix it on Monday. - The content server is not yet fully Node 4 compliant so we decided no ES2015 in our functional tests yet. <sniff> - We need some additional functional tests around CSS and SRI - the above mentioned CSS/SRI issue went uncaught by our tests. - Vlad is wondering how we can determine whether a sessionToken displayed in the Apps/Devices view is for Sync. Anyone have ideas? [6] Shane [1] - https://github.com/mozilla/fxa-content-server/pull/4210 [2] - https://github.com/mozilla/fxa/pull/193 [3] - https://github.com/mozilla/fxa-auth-mailer/pull/215 [4] - https://github.com/mozilla/fxa-shared/pull/8 [5] - https://signin-unblock.dev.lcip.org [6] - https://github.com/mozilla/fxa-content-server/issues/4212
_______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
