Brad Gignac bradgignac

Implement Exponential Backoff

The DynamoDB documentation recommends implementing client-side retries with exponential backoff when a ProvisionedThroughputExceededException is received. My team has already implemented this as a wrapper around Vogels, but we'd love to push this feature down into Vogels if you're open to the contribution.

The model definition might be good place to enable this feature. For example:

var Account = vogels.define('Account', {
 hashKey : 'email',

Amazon API Gateway Supports API Definition Import and Export Posted On: Dec 18, 2015

AWS IoT Now Generally Available Posted On: Dec 18, 2015

Enhanced Monitoring is now available for Amazon RDS MySQL, MariaDB and Amazon Aurora Posted On: Dec 18, 2015

AWS Config Rules - now broadly available to all customers

Keybase proof

I hereby claim:

I am bradgignac on github.
I am bradgignac (https://keybase.io/bradgignac) on keybase.
I have a public key whose fingerprint is 6264 D1D2 83CD C557 D0DA 83C4 4A60 194A 845E E54E

To claim this, I am signing this object:

I've been taking a look at how navigation is currently implemented, and I had a few ideas for how it can be improved. I'm opening this issue to gather feedback on these ideas and figure out what changes should be made. Out of the box, Bootstrap supports the following options for navbars:

Multiple Content Types: links, brand images, forms, buttons, and text
Multiple Content Alignments: navbar-left and navbar-right
Multiple Positions: fixed to top, fixed to bottom, static to top
Multiple Background Colors: navbar and navbar-inversed

On the other hand, Canon has four different styles of navigation:

Utility Navigation

	/* Providers */

	provider "aws" {
	region = "us-west-2"
	}

	/* Variables */

	variable "name" {
	default = "XXXXX"

	let sizzle = require('sizzle');
	let React = require('react/addons');
	let TestUtils = React.addons.TestUtils;

	global.findAll = function (root, selector) {
	return TestUtils.findAllInRenderedTree(root, function (component) {
	let node = React.findDOMNode(component)
	return sizzle.matchesSelector(node, selector);
	});
	};

	Multiple environments are a staple of software development projects, but do they
	actually help us make better software? Do they help us get it into the hands of
	customers faster? In this talk, I'll look at the goal of every development team
	-- delivering quality software. I'll review how environments have historically
	helped achieve this goal as well as the problems they have caused along the way.
	Finally, I'll look at alternative techniques that can be used in lieu of
	environments.

	var Dispatcher = require('flux/dispatcher');
	var PopoverForm = require('canon-react/popoverForm');

	var CreateNetworkPopover = React.createClass({
	render: function () {
	<CreateNetworkPopover>
	<PopoverForm onSave={this.create} onCancel={this.dismiss} open={this.state.open}>
	// Custom popover content goes here.
	</PopoverForm>
	</CreateNetworkPopover>

	import argparse
	import csv
	from datetime import date, timedelta
	from itertools import groupby

	import requests


	parser = argparse.ArgumentParser(description="Generate dashboard graph.")
	parser.add_argument('domain', type=str, help="Mailgun domain")

	# Usage:
	# python recipientsearch.py find query --key MYMAILGUNKEY
	# python recipientsearch.py unsubscribe query --key MYMAILGUNKEY
	# python recipientsearch.py destroy query --key MYMAILGUNKEY

	import argparse
	import requests
	import urllib

	FIND = 'find'