biancadanforth

diff --git a/packages/fxa-auth-server/lib/payments/stripe.ts b/packages/fxa-auth-server/lib/payments/stripe.ts
index 23ef5812a..84be94e75 100644
--- a/packages/fxa-auth-server/lib/payments/stripe.ts
+++ b/packages/fxa-auth-server/lib/payments/stripe.ts
@@ -833,24 +833,9 @@ export class StripeHelper {
     customerId: string;
     postalCode: string;
     country: string;
-  }): Promise<boolean> {
-    try {

biancadanforth

/* This Source Code Form is subject to the terms of the Mozilla Public
 * License, v. 2.0. If a copy of the MPL was not distributed with this
 * file, You can obtain one at http://mozilla.org/MPL/2.0/. */

/* eslint-disable max-len, arrow-body-style */
import {linearScale} from "fathom-web/utilsForFrontend";
import {dom, out, rule, ruleset, score, type} from "fathom-web";

const coefficients = {
  "paragraph": [

biancadanforth

/* This Source Code Form is subject to the terms of the Mozilla Public
 * License, v. 2.0. If a copy of the MPL was not distributed with this
 * file, You can obtain one at http://mozilla.org/MPL/2.0/. */
import { AuthLogger } from 'fxa-auth-server/lib/types';
import { ACTIVE_SUBSCRIPTION_STATUSES } from 'fxa-shared/subscriptions/stripe';
import { StatsD } from 'hot-shots';
import stripe from 'stripe';
import Container from 'typedi';

import { CurrencyHelper } from '../lib/payments/currencies';

biancadanforth

If upgrading (say from a $10/month to a $20/month plan 3 days into the subscription):

1. Calculate the fraction of the period used to this point under the previous plan, x.

3 days /30 days = 0.1 = x

Note: This is approximate, since months can have different numbers of days, there are leap years, etc.

2. Multiply x by the previous plan's billing amount, amount_prev to get how much to credit the customer back, credit.

biancadanforth

const fetch = require("node-fetch");
const config = {
  paypal: require("./paypal-config")["DEV"],
};

const PAYPAL_SANDBOX_NVP_BASE_URL = "https://api-3t.sandbox.paypal.com/nvp";
const nvpUrl = new URL(PAYPAL_SANDBOX_NVP_BASE_URL);
const params = {
  USER: config.paypal.USER, // Merchant username
  PWD: config.paypal.PWD, // Merchant password

biancadanforth

const fetch = require("node-fetch");
const { getPayPalBearerToken } = require("../../github/bin/get-oauth2-token/bin/getOAuth2Token");

const PAYPAL_SANDBOX_BASE_URL = "https://api-m.sandbox.paypal.com";

async function postToPayPalAPI(apiPath, body) {
  const bearerToken = await getPayPalBearerToken();
  const metadata = {
    body,
    headers: {

biancadanforth

What happens after Outreachy?

Disclaimer: These thoughts are my own (Bianca Danforth) based on my experience starting as an Outreachy at Mozilla and now working as a Senior Software Engineer.

Congratulations! You’ve just completed your Outreachy internship. You may be wondering: Where do I go from here? How do I get a job in software engineering? Below are a set of steps I recommend based on my own experience.

Introspect

• Identify goals
  • What are your professional goals?
  • If you're not sure where to start, ask other people you admire what their professional goals are.
• Identify skills
• What skills do you need to achieve your goals (those you already have, those that you need to improve, and those you need to learn)?

biancadanforth

Front End Performance and Profiling Team Session

May 11, 2020

Mozilla performance communication channels

• #perf on Slack
• Firefox Profiler on Matrix

General

• MDN Performance docs
• Performance best practices for Firefox Engineers

biancadanforth

diff --git a/Users/bdanforth/.hgrc b/Users/bdanforth/.hgrc-mythmon
index d2d9e52..e32a8cb 100644
--- a/Users/bdanforth/.hgrc
+++ b/Users/bdanforth/.hgrc-mythmon
@@ -26,13 +26,11 @@ absorb =
 js-format = /Users/bdanforth/.mozbuild/version-control-tools/hgext/js-format
 shelve = 
 [alias]
-wip = log --graph --rev=wip --template=wip
-smart-annotate = annotate -w --skip ignored_changesets

biancadanforth

Since Bug 1595244 landed yesterday (based on the model at bff6995c), we have started to get some telemetry regarding how long it takes to show the password generation UI. We also did some profiling this afternoon. Taking both of these together, we think it would be prudent to make some relatively straightforward changes to the ruleset to improve its performance.

The following numbers are based on profiling Nightly, taking an average of 5 runs for a locally hosted registration page. Taken together, these sets of changes would speed up the model by about 42%, and there may be more low hanging fruit as well.

The diff below would speed up the model by about 25%. This would not require any retraining.

diff --git a/toolkit/components/passwordmgr/NewPasswordMode