jconwell

import asn1

"""
This example shows two different ways to write arbitrary sized byte arrays into
ASN.1 Null fields. This could be used when manually generating x509 certificates that
contain some kind of data payload
"""

input_msg = """Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nam nec sem eros. Fusce mattis nunc eget eros viverra, 
ac ultrices elit pellentesque. Proin quis neque vel ante vehicula egestas. Duis vestibulum nibh augue, non dapibus 

jconwell

Pretty simple once you know how.

Step 1: In IntelliJ, create a new remote debug configuration.  Name it something ElasticSearchy.  All of the default values should be fine.  The only thing you need to change is the Host value.  If ElasticSearch is gonna be running locally, just use "localhost", otherwise use the IP address of the remote machine ElasticSearch is gonna run on

Step 2: When starting ElasticSearch, just add a -D argument with the standard java remote debug values like so:
bin/elasticsearch -D "-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"

ElasticSearch will start and if suspend is set to 'y', it'll pause execution until you have attached the IntelliJ debugger.

Step 3: In IntilliJ, run the remote debug configuration you created in step 1.

jconwell

function getEmails() {
  // get all messages
  var allAddresses = [];
  var start = 0;
  var emailCount = 500;
  var doIt = true;
  while (doIt) {
    var emails = GmailApp.getMessagesForThreads(GmailApp.search('after:2012/9/1', start, emailCount))
    start += emails.length;
    doIt = emailCount == emails.length;

jconwell

AKKA Test Patterns for Java

NOTE: These patterns assume you have a working understanding of Akka's JavaTestKit

Testing Actors In Complete Isolation

AKKA is all about building hierarchies of actors to represent a system. I've found this is a great way to decompose, design, and if needed distribute a system. This means your system becomes a hierarchy of actors, where parent actors create and manage their child actors, and child actors either carry out some unit of work, and/or themselves become parent actors.

But this can be a bit of a pain when it comes to writing tests for your actors. For example, say we have an actor, actorA, who in turn creates one or more child actors. I could have actorA create its child actor(s) as part of its instantiation. This is attractive especially if I know the exact child actors its going to create.

jconwell

package com.turbo.akka;

import akka.actor.UntypedActor;
import akka.event.Logging;
import akka.event.LoggingAdapter;

import java.util.HashMap;
import java.util.Map;

/**

jconwell

package com.turbo.akka;

import akka.actor.ActorRef;
import akka.actor.Props;
import akka.actor.UntypedActor;
import akka.event.Logging;
import akka.event.LoggingAdapter;

/**
 * Utility actor that does nothing but take a Props and create

jconwell

package com.turbo.akka;

import akka.actor.ActorRef;
import akka.actor.UntypedActor;

 /**
 * Simple actor that takes another actor and forwards all messages to it.
 * Useful in unit testing for capturing and testing if a message was received. 
 * Simply pass in an Akka JavaTestKit probe into the constructor, and all messages 
 * that are sent to this actor are forwarded to the JavaTestKit probe