djm

Problem: you've created a Custom Authorizer Lambda and have hooked it up with Amazon AWS's API Gateway.
But now all of your responses return the following HTTP response with the "AuthorizerConfigurationException"
and your Cloudwatch logs for your Authorizer function are next to useless..

-----

HTTP/1.1 500 Internal Server Error
Connection: keep-alive
Content-Length: 16
Content-Type: application/json

djm

<template>
    <div>
        <label v-if="label" class="form-label" :for="`date-input-${_uid}`">{{ label }}:</label>
        <input v-bind="$attrs" class="form-input" :id="`date-input-${_uid}`" :class="{ error: error }" type="text" ref="input" :value="value" @change="change" @keyup="change">
        <div v-if="error" class="form-error">{{ error }}</div>
    </div>
</template>

<script>
import pikaday from 'pikaday'

djm

defmodule Test do
  def thing() do
    1+1
  end
  
  defmacro my_macro do
    quote do
      1 + 1
    end
  end

djm

from jobs import send_welcome_email

# ...

def register_user():
    user = do_the_registration()
    send_welcome_email.transaction_aware_delay(user.id)
    # or
    # send_welcome_email.request_aware_delay(user.id)
    

djm

"""
Utilities for working with bulk data and batches.
"""
import itertools


def batches(items, batch_size=500):
    """
    Given an iterable of items and a batch size, yield individual lists
    of items of maximum length `batch_size`.

djm

from typing import List, Sequence
 
 
def unique_with_order(sequence: Sequence) -> List:
    """
    Returns the original sequence as a list with duplicates removed
    but, unlike simply using set, the original order is retained.
    """
    seen = set()
    return [x for x in sequence if not (x in seen or seen.add(x))]

djm

FROM node:8
WORKDIR /home/node/app

ADD https://github.com/Yelp/dumb-init/releases/download/v1.1.1/dumb-init_1.1.1_amd64 /usr/local/bin/dumb-init
RUN chmod +x /usr/local/bin/dumb-init

COPY package.json yarn.lock ./
RUN yarn --pure-lockfile
COPY . .

djm

Introduction

To get rq workers talking to opbeat at this current time, you must use a custom rq exception handler and add it to the chain that the worker accepts. This allows us to call opbeat synchronously and avoid the current issues with the opbeat library's async workers.

Both of the examples below keep the original rq exception handler functionality of moving a failed job to the failed queue, but this is optional - if you only want opbeat logging then just don't pass the move_to_failed_queue handler.

Note that we send a lot of extra information about the job itself (see _get_job_details) but this is not a requirement, the stack you get is useful enough without it.

With django-rq (>=0.9.5)

djm

# removes all tags from a git remote
# 1. `git ls-remote --tags origin` - lists all the tags at origin: '<hash> refs/tags/<tag>'
# 2. `awk '/^(.*)(\s+)(.*[a-zA-Z0-9])$/ {print ":" $2}'` - extract the ':/ref/tags/<tag>' from each
# 3. `xargs git push origin` - run 'git push origin :/ref/tags/<tag>' against each tag
git ls-remote --tags origin | awk '/^(.*)(\s+)(.*[a-zA-Z0-9])$/ {print ":" $2}' | xargs git push origin

djm

test:
  override:
    - bundle exec rspec spec

deployment:
  acceptance:
    branch: master
    commands:
      - ./script/heroku_deploy.sh <ACCEPTANCE_HEROKU_APP>:
          timeout: 300