• integrate lock widget
• change name of tenant "gitstats-frontend-dev" right now -- if it is user facing
• increase expiry time for logging out
• "your teams" in the top nav
• "loading your teams" after log in
• test sign up flow

• call API from frontend code
• update authorizer to bypass home page calls
• before caching, add date as param to url (ensure url has all necessary params)
• save results to cache, define the key to cover invalidation scenarios
• fetch results from cache whenever available
• check loader in homepage view

Potential improvements

• Explain what the next step is about
• Why are the permissions required
• Which repos must be selected

try github/Microsoft for example. we probably need to paginate our APIs to support such cases

• Not clear that this includes approvals - maybe rename this to time to review?
• User needs visibility across members - to be able to prompt them to speed up

example

Server-Timing: db;dur=201.098919, tpl;dur=301.271915;desc="Templating", geo;dur=404.520988;desc="Geocoding"

• show status of PR next to the name
• PR name should feel click-able
• change row background on hover to improve readability
• convert dots into lines
• chart filters: open, merged, reviewed, no reviews, slow to merge

• add user to cache key
• add date (week start) to cache key

on the stats endpoint

2018-09-29 19:21:20.423 (+05:30)	be909871-c3ee-11e8-bf8f-c9206e69ef22	(node:1) UnhandledPromiseRejectionWarning: StatusCodeError: 429 - {"statusCode":429,"error":"Too Many Requests"}
    at new i (/var/task/webpack:/node_modules/request-promise-core/lib/errors.js:32:1)
    at G.callback (/var/task/webpack:/node_modules/request-promise-core/lib/plumbing.js:104:1)
    at G.e.callback.t.callback [as _callback] (/var/task/webpack:/node_modules/request-promise-core/lib/plumbing.js:46:1)
    at G.t._callback.t.callback.t.callback [as callback] (/var/task/webpack:/node_modules/request/request.js:185:1)
    at emitTwo (events.js:126:13)
    at G.emit (events.js:214:7)
    at G.<anonymous> (/var/task/webpack:/node_modules/request/request.js:1157:1)
    at emitOne (events.js:116:13)
    at G.emit (events.js:211:7)
    at IncomingMessage.<anonymous> (/var/task/webpack:/node_modules/request/request.js:1079:1)
2018-09-29 19:21:20.423 (+05:30)	be909871-c3ee-11e8-bf8f-c9206e69ef22	(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 12)

the current VPC configuration on AWS is turning out to be costly -- the NAT Gateway is charged by the hour, and is required for the Lambda functions to make API calls outside the network (to GitHub eg). Can we explore reverting to the earlier non-VPC configuration, without the gateway, but still use ElastiCache?