Corey O'Connor

You say workaround but I see an interface proposal and default implementation. ;) I was expecting `AnyRef` not `Object`. Is `Object` more appropriate when referring to GC-able references?

One option is to sidestep s3 resolver entirely and load the plugin over http served from s3: ~~~ resolvers += Resolver.url( "glngn server releases", url("https://glngn-server-releases.s3.amazonaws.com/releases") )(Resolver.ivyStylePatterns) addSbtPlugin("glngn" % "sbt-glngn" %...

> > check if a process with that pid exists > > if no process with that pid exists for a period of time then delete the pid file and...

I found this to be an effective work around: ~~~ val verbatimAtom = new xml.Atom(verbatimText) { override def buildString(sb: StringBuilder): StringBuilder = sb.append(importMapStr) } ~~~

Interestingly a similar situation arose for an amazon library of an abstraction over dynamodb. In that case, the library persisted large blobs to an S3 bucket. All logical records were...

this design would result in the features being: * 400 kb limit for DDB only * prerequisites: IAM with DDB access; DDB table creation x 2 * no limit for...

The j5ik2o dynamodb plugin implementation: * https://github.com/j5ik2o/akka-persistence-dynamodb/blob/master/src/main/scala/com/github/j5ik2o/akka/persistence/dynamodb/query/dao/ReadJournalDaoImpl.scala looks to use a polled scan request lifted to a stream.

Looking into this further. I agree with https://github.com/akka/akka-persistence-dynamodb/issues/50#issuecomment-302961050 * DynamoDB streams are efficient for following recent updates but not sufficient by themselves. The added operations cost is also worth keeping...

Thank you for your patience. I'm working to review this this week. Looks like I still have some CI fixes to push first.

oof. last time I use the web UI to edit. Trying to fix that transient test error. My fix was definitely not correct. Hm. I still think the hypothesis is...