Steven Hawkins

@vreuland thank you for looking into this as well. > Using the test, I could reproduce the error (rows that have disappeared) but interestingly, I am also getting the "Double...

> But again, on my machine, running your test several times, I had several different outcomes: Running with a build from https://github.com/h2database/h2database/commit/11a0d60bcb5ccd5989b83f999704a1b6549a5681 reproduces the Double Mark error (seems pretty infrequent),...

> But generally the idea that record the transformation based on response is great. > > Wonder if this would not require optimistic locking to be absolutely correct, is when...

> @shawkins maybe we could also take a look together on our community meeting. Sounds good, I will join the next one.

> missing fields in the generated Builder: I encourage you to open an issue to the relevant project: [sundrio](https://github.com/sundrio/sundrio) There's several things that don't work well here with sundrio. It...

@fengyinqiao I understand that the field name is not determined by you, my comments are more about what will currently work with sundrio. For this case to work without changes...

> I'd suggest this should be worded differently. We're not deprecating EXTERNAL and ALL. We're deprecating the whole SSL Required option. And this should be also reflected in the UI....

> @shawkins I think the proper new way of deprecating things is to wrap it in a new Profile Feature that will be enabled by default but deprecated right away....

> Does it make sense? No, because that is new behavior. A deprecated feature is not enabled by default. That currently only happens if it's marked as DEFAULT, or PREVIEW...

> Yeah, seems like that's what needs to be done. For the new release scheme where we're not allowed to make breaking changes so often, we definitely need to be...