Odg: Region is not created on one of the servers

I think that there can be a problem if we change to first add it to cluster config and then do distribution to existing servers. Now, when the "create region" command is executed it got all servers from the view and sends all of them to start creating a region with parameters specified in the c

Re: Region is not created on one of the servers

Hi Mario, I think your assessment of the problem is correct. Thinking about it, there is no simple (correct) way to easily solve this. Given that there are too many variables in play, users making configurational changes, whilst servers are coming up. Now, that said, I think we should address

Geode-9621: Spotless overstepping its boundary of formatter

Hi there Geode Devs, Recently GEODE-9621 was introduced onto the develop branch. This new feature introduces a new bug where `spotlessApply` will remove all version dependencies out of gradle. I assume this is to combat the risin

Re: Geode-9621: Spotless overstepping its boundary of formatter

Currently there is no way to exclude certain code blocks from the malicious code formatter. Therefore, my tests that require a specific hardcoded version of Spring to be used, will always either fail the validation or tests will fail due to spotless changing my testing scenario by affecting the

Re: Geode-9621: Spotless overstepping its boundary of formatter

Hi there Robert, Yes, you did work with me, but the solution to add my custom versions of jars that I want to test with, into the `DependencyConstraints` file just feels like the wrong approach. The prior art you refer to, is a specific version of tomcat we want each module to use. It is no di