eddiewebb

Keybase proof

I hereby claim:

• I am eddiewebb on github.
• I am edwardawebb (https://keybase.io/edwardawebb) on keybase.
• I have a public key whose fingerprint is 4762 7E46 83E9 82CC 2591 0D28 01F3 D3D7 0CA9 2044

To claim this, I am signing this object:

eddiewebb

// This allows you to call methods wrapped in a timer for profilling. 
// I used in a scenario where my abstract class delegated back to concrete implementations, and wanted to be aware of duration.
// Because timer runs in a lambda, it doesn't require any special treatment to see/manipulate current context/scope.

public abstract class AbstractClass{

  public final loadDependencies(Map<String, Object> map){  
    //here we call some methods, they could be anywhere.
    ChainResultsSummary results = timing("getChainResultsSummary",() -> getChainResultsSummary(map));
    ImmutableChain chain = timing("getImmutableChain",() -> getImmutableChain(map));

eddiewebb

workflows:
  version: 2
  build-deploy:
    jobs:
      - build
      
version: 2
jobs:
  build:
    docker:

eddiewebb

#! /bin/bash

#
# This file will filter all s3 objects where the key/path contains a specific pattern and apply the provided tag.
# Results are split into X number of backfground processes, each tagging 1000 objects 
#


BUCKET_NAME="YOURBUCKET"
function tagObjects {

eddiewebb

#! /bin/bash

#
# This script pulls recent circleci build history, using jq to filter by ssh rebuilds, and printing the summary
# Requires `jq` and a CIRCLE_TOKEN
#


CCI_PROJECT="orgname/projectname"

eddiewebb

GH_TOKEN="1234"
ORG_NAME="some-org"

curl -H "Authorization: token ${GH_TOKEN}" https://api.github.com/orgs/${ORG_NAME}/repos | jq -r '.[].url' > /tmp/repos

rm /tmp/repos 2>/dev/null
while read REPO;do
curl -H "Authorization: token ${GH_TOKEN}" ${REPO}/contributors 2>/dev/null | jq -r '.[].login' >> /tmp/users
done < /tmp/repos

eddiewebb

#!/bin/bash

#
#  This script is a workaround to a Replicated issue in which the configuration sections do not appear in the admin console.
#  It should be run on the services box from a new/clean directory where a backup will be created.
#


if [ ! -f metrics.txt ];then
  echo "Please run this script in a clean directory with a 'metrics.txt' file containing desired telegraf config"

eddiewebb

#!/usr/bin/env bash
#
# Download all artitacts for given build, mimicing structure locally.
#
# Batch size is slighly misleading, as it;s only how many URLs to attempt before momentary pause
#
# Can be used on CCI builds with parallelism and will only download the files for matcing index.
#
#
USAGE="$0 username/repo 123 [bitbucket] [batch_size]"

eddiewebb

What

A 'fix' for the notoriously poor reading issues of DHT hygrometer sensors from Python / Raspberry Pis.

Why

I've used the cheap DHT sensors on a few projects and always find the "yeah they're unreliable, just keep trying" and that sucks. How do opther devices work using these sensors? Priority.

So these process changes have, for me, worked to give my python process the realtime CPU & IO access to meet the strict timing requirements of a DHT sensor.

eddiewebb

Pulls Insight Contribution count from JPD

• Container == issue, and is the ARI id formatted as <ari>/issue/<id> ari:cloud:jira:123456-7890-4681-8327-40539f3855d1:issue/129565

• Project ID similar but using /project/ ari:cloud:jira:123456-7890-4681-8327-40539f3855d1:project/11277

Grpahql