mdindoffer

+1 for this. For comparison Cap'n'proto-java does indeed respect the bit length and outputs java `byte` variables. The same applies to `short` primitive type for `uint16`. This wastes memory.

Thanks for the thorough explanation. Yes, the whole point of this is to reduce overhead / increase performance, which is lost when trying to write reactive code in a defensive/foolproof...

A shower thought of today, if I may: the error-throwing runtime variant of `assertPublishedOn` could be useful for `reactor-test` / `StepVerifier` as well. One could test in unit/integration tests whether...

I just want to add here that this is blocking us (and probably others) from upgrading to 1.1.4. What's worse is that due to 1.1.3 depending on old netty, we...

@OlegDokuka I understand this is not a priority for you, and that's fine. But we'd really love to upgrade the rest of the reactive stack at least (i.e. bumping the...

> This issue is stale because it has been open 6 months with no activity. Please comment or label `not-stale`, or this will be closed in 14 days. Not stale,...

I did not manage to create a reproducible IT, but I made a tiny reproducible project: https://github.com/mdindoffer/gh-221/blob/master/pom.xml There's literally just an empty pom file with this (for preservation purposes): build...

Oh actually, I took a second look, and it's pretty simple really. `maven-scm-provider-jgit` 2.1.0 depends on `maven-scm-provider-git-commons`, and is calling `setLastChangedDateTime` which is implemented `@since 2.1.0`. All the while `buildnumber-maven-plugin`...

> @mdindoffer version 3.2.1 was released ... can we close it? Oh yes, sorry. I can confirm the latest version works just fine :+1:

> Cases that leave hero without any army should be off by default - this is pretty much a bug in H3, no need to replicate it. Not against game...