ktheory

Event,Status,Event category,Region / ZoneInfo,Start time,Last update time,Affected resources
Operational issue - Billing (Global),Closed,Issue,-,"June 15, 2022 at 9:15:54 PM UTC-4","June 15, 2022 at 9:53:46 PM UTC-4",-
Operational issue - ELB (N. Virginia),Closed,Issue,us-east-1,"June 9, 2022 at 9:52:48 PM UTC-4","June 10, 2022 at 2:38:31 AM UTC-4",-
CertificateManager renewal state change,Completed,Scheduled change,us-east-1,"June 10, 2022 at 1:17:02 AM UTC-4","June 10, 2022 at 1:17:04 AM UTC-4",1 entity
Operational issue - Route53 (Global),Closed,Issue,-,"May 26, 2022 at 10:21:35 PM UTC-4","May 27, 2022 at 1:24:40 AM UTC-4",-
Operational issue - Billing (N. Virginia),Closed,Issue,us-east-1,"May 25, 2022 at 5:22:21 PM UTC-4","May 25, 2022 at 7:05:09 PM UTC-4",-
Operational issue - Billing (Global),Closed,Issue,-,"May 25, 2022 at 6:53:50 PM UTC-4","May 25, 2022 at 6:58:45 PM UTC-4",-
Operational issue - Kinesis (Stockholm),Closed,Issue,eu-north-1,"May 19, 2022 at 2:44:47 PM UTC-4","May 19, 2022 at 3:29:58 PM 

ktheory

Motivation

I wanted to implement Sanctuary's gets function to safely access a nested path on an object, but using Folktale 1.0's functions.

This implementation relies on Folktale's core.operators.get function. Though it returns a Maybe instead of value | undefined.

The gets method is particular handy for AWS Lambda functions, where the passed event is often a deeply-nested object.

ktheory

A tale of two curries

I'm considering how best to curry functions in JS (w/out an external library).

I can see two ways of doing so, and am interested in what others see as the advantages/disadvantages of each approach:

Option 1: curry-first design

Write functions that only take a single argument and return other functions:

ktheory

Javascript request yak shave

I wanted to easily make HTTP requests (both GET & POST) with a simple interface that returns promises.

The popular request & request-promises package are good, but I wanted to figure out how to do it w/out using external dependencies.

The key features are:

• the ability to set a timeout
• non-200 responses are considered errors that reject the promise.
• any errors at the TCP socker/DNS level reject the promise.

ktheory

AWS ECS auth with AppRole and S3

I'm interested in having AWS ECS services authenticate to Vault (like issue #1298).

Here's an idea for how to implement ECS auth using recent features, like Vault's AppRole auth backend, and IAM roles per ECS task.

I'm eager to hear if folks think it's a reasonable approach.

ktheory

#!/usr/bin/env ruby

require 'benchmark'
$: << './lib'
require 'rack'

n = 1_000_000

response = Rack::Response.new
response.status = 301

ktheory

FROM ubuntu:14.04

# A proof-of-concept for Riemann
# Based on http://kartar.net/2014/12/an-introduction-to-riemann/

RUN apt-get update && \
  apt-get install -y software-properties-common && \
  apt-add-repository -y ppa:brightbox/ruby-ng && \
  apt-get update && \
  apt-get install -y ruby-switch ruby2.2 ruby2.2-dev && \

ktheory

class MyClass
  # How do I test #run without actually invoking `do_thing1` and `do_thing2`?
  # I'd like to mock them. But Minitest only allows stubbing entire objects,
  # so I can't mock the methods without changing the object under test.
  def run
    do_thing1
    do_thing2
  end
  
  def do_thing1

ktheory

Keybase proof

I hereby claim:

• I am ktheory on github.
• I am ktheory (https://keybase.io/ktheory) on keybase.
• I have a public key whose fingerprint is EEDA 1708 5F77 0AFC B7CE 3DB2 A0BE 5958 E6B6 21FE

To claim this, I am signing this object:

ktheory

Copyright 2014 Kickstarter, Inc.

Released under an MIT License.