dispalt

package webm

import scala.collection.{GenMap, GenTraversableOnce}
import scala.language.experimental.macros
import scala.reflect.macros.blackbox
import scala.scalajs.js
import scala.scalajs.js.|

object FunctionMacro {

dispalt

diff --git i/api/src/main/scala/com/goodcover/gql/ClaimSchema.scala w/api/src/main/scala/com/goodcover/gql/ClaimSchema.scala
index f522db989..f895e3f40 100644
--- i/api/src/main/scala/com/goodcover/gql/ClaimSchema.scala
+++ w/api/src/main/scala/com/goodcover/gql/ClaimSchema.scala
@@ -117,6 +117,7 @@ class ClaimSchema(nodeInterface: InterfaceType[Ctx, AnyRef], A1VersionedPolicyTy
       Field("policy", OptionType(A1VersionedPolicyType), resolve = _.value.selectedPolicy),
       Field("documents", ListType(ClaimDocumentType), resolve    = _.value.documents),
       Field("lossPlace", OptionType(PlaceType), resolve          = _.value.lossPlace),
+      Field("foo", OptionType(IntType), resolve                  = _ => 1),
       // TODO: Add events here and to [[ClaimEventInterface]]; these need to be kept in sync

dispalt

import $ivy.`org.clulab::processors-main:6.1.3`
import $ivy.`org.clulab::processors-corenlp:6.1.3`
import $ivy.`org.clulab::processors-odin:6.1.3`
import $ivy.`org.clulab::processors-modelsmain:6.1.3`
import $ivy.`org.clulab::processors-modelscorenlp:6.1.3`
import $ivy.`com.lihaoyi::pprint:0.5.3`

import org.clulab.odin.ExtractorEngine
import org.clulab.processors.Processor
import org.clulab.processors.clu.CluProcessor

dispalt

/*
This is a macro that takes a GQL statement and produces js. I achieve this 
by forking out to node and executing the babelRelayPlugin.  This solution is sub-par for
3 big reasons:

  1) Naming - Since it executes outside the "scope" (aka independently). I have to do some error prone things.
   * use the js.constructorOf[FooClass] and assign it to a global variable like global.FooClass = js.constructorOf... 
  2) Static stuff, which is due for sjs inclusion, so not huge.
  3) Eval - It turns into strings that get evaluated... Is there a better way to integrate?
  

dispalt

Keybase proof

I hereby claim:

• I am dispalt on github.
• I am dispalt (https://keybase.io/dispalt) on keybase.
• I have a public key whose fingerprint is 6A46 202D 4540 9B3E 1202 AB9B 32EF C74C 37D0 7BE3

To claim this, I am signing this object:

dispalt

#!/bin/bash

FRAMEWORK_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )/.."
DIST_NAME=hdfs-mesos
DIST_VERSION=0.1.1
DIST=$DIST_NAME-$DIST_VERSION

export MESOS_HDFS_DATA_DIR=${MESOS_HDFS_DATA_DIR:-"/tmp/hdfs/data"}
export MESOS_HDFS_SECONDARY_DATA_DIR=${MESOS_HDFS_SECONDARY_DATA_DIR:-"/var/run/hadoop-hdfs"}
export MESOS_HDFS_NATIVE_HADOOP_BINARIES=${MESOS_HDFS_NATIVE_HADOOP_BINARIES:-false}

dispalt

### Keybase proof

I hereby claim:

  * I am ddispaltro on github.
  * I am dispalt (https://keybase.io/dispalt) on keybase.
  * I have a public key whose fingerprint is 6A46 202D 4540 9B3E 1202  AB9B 32EF C74C 37D0 7BE3

To claim this, I am signing this object:

dispalt

# React Nested Router is only distributed with CommonJS.
# To get a standalone version wrapped in a Universal Module (AMD/CJS/Global) run the browserify command below.
# If there's no module system it'll export a global called ReactNestedRouter.
# This assumes you've got React on the page in some other way (AMD, Global, etc)

$ npm install browserify
$ npm install react-nested-router
$ ./node_modules/.bin/browserify -r react-nested-router/modules/main -x react -s ReactNestedRouter -o react-nested-router.js

dispalt

Keybase proof

I hereby claim:

• I am ddispaltro on github.
• I am dispalt (https://keybase.io/dispalt) on keybase.
• I have a public key whose fingerprint is D7BA 065B BC91 DAF7 7185 BAD5 63E1 DB6E E2E9 2BC0

To claim this, I am signing this object:

dispalt

Dear Dan:
 
We are writing to notify you that between approximately March 4, 2013 and March 10, 2013, an unauthorized third party may have obtained access to our internal management systems associated with our Agile servers and to our Agile customers’ profiles.  The information that could have potentially been exposed includes your name, email address, phone number and mailing address.  We are communicating to each of our potentially affected customers that this unauthorized access may have occurred.  We want to emphasize that we do not know that your information was in fact accessed, but because of the potential exposure, we want to make sure you take appropriate action.    
 
Internap values your business and the privacy of your information and regrets that we have to write you about this matter.  We have notified law enforcement and are investigating how this attack occurred so that we can prevent similar ones in the future.
 
We have already taken specific operational steps as additional precautionary mea