Gabriel Francisco
Gabriel Francisco
I guess #347 solved this issue.
@gunnarmorling sorry for the delay to answer your first comment. I also have been incredibly busy lately, but this weekend I'll check your review and I will work on this...
+1 This feature is very useful when you want to publish a snapshot image, test it and only then generate the release version.
Seems fine to me. ;)
I guess he's talking about this, but for Scala: https://github.com/Microsoft/vscode-java-debug. I'm not familiar with VS, can anyone tell if it is trivial to fork this and adapt to work with...
Yes, I have configured it. This is my app in marathon: ``` json { "id": "/hello-java", "cmd": "java -jar hello-java-all* $HOST $PORT", "cpus": 0.1, "mem": 32, "disk": 20, "instances": 5,...
I just checked and sometimes on restart all the instances are "INI" and none L7OK/200. When I check marathon I always see at least one healthy instance.
> Batching through `.add() `would only properly work if the SQL doesn't change. @mp911de, correct me if I'm wrong, but the SPI has two ways of batching, right? One that...
I think it has to do with `offset.storage` properties. There's other thing we have to look up to see if it fits well with Akka Streams. I'm afraid it relies...
It seems like the behavior of `RecordCommitter` is just like you said. This way will be easy to implement backpressure. I'll run some tests myself to be sure about this...