Aleks Seovic

@carl-mastrangelo I can think of another option: 1. Change the package name to `io.grpc.context` in `grpc-context` module. That will fix the split package issue going forward, but will break existing...

In the meantime, we have repackaged `grpc-java` (version 1.22.1) as a Java 9+ module as part of Helidon, in order to support our gRPC framework implementation, and have made it...

I would very much prefer if the workaround we had to implement was part of `grpc-java` itself, instead of being "our" module that does nothing but repackages `grpc-java` artifacts. While...

@cjohnstoniv What you are proposing is effectively the same as option 1 (short term) and option 2 (long term), which were rejected by @carl-mastrangelo because "they would bring dependencies back...

The problem is that the only backend that has messaging support at the moment is Redis, and we don't have messaging support in Helidon yet, so maybe this should wait...

Sure, let me do that and I'll ping you back here.

@thegridman I think you may be missing the (valid) point @javafanboy is trying to make: scaling in one node at a time, the way both the Operator and AWS auto...

@javafanboy Yes. I've created a JIRA internally for this work back in May, and we've had a few discussions on how we would actually do it, and have agreed on...

Actually, while the existing changes look good, I think some are still missing: `getHighUnits` and `setHighUnits` also need to take unit factor into account: ```java @Override public int getHighUnits() {...

@rlubke Looks like we'll have to do a manual patch in P4. Automated PR merge still doesn't work... :-( @thegridman This may be a good PR to use to sort...