Wolfgang Werner

Happens for me as well, 9 out of 10 logins time out.

The simple option is to reload data from the client from time to time, either scheduled or tied to specific user actions. A cool alternative would be to leverage SSEs...

Some pointers from @VaughnVernon copied in from slack for future reference: * https://github.com/antlr/grammars-v4 * https://github.com/antlr/grammars-v4/blob/f40d77f85ee8a299d309cdcd15bfff5041bc44ad/java/java/JavaParser.g4#L286 * https://github.com/antlr/grammars-v4/blob/f40d77f85ee8a299d309cdcd15bfff5041bc44ad/java/java/JavaLexer.g4#L87 * https://github.com/antlr/grammars-v4/blob/f40d77f85ee8a299d309cdcd15bfff5041bc44ad/java/java/JavaParser.g4#L372 * https://github.com/antlr/grammars-v4/blob/f40d77f85ee8a299d309cdcd15bfff5041bc44ad/java/java/JavaParser.g4#L584 * https://github.com/antlr/grammars-v4/blob/f40d77f85ee8a299d309cdcd15bfff5041bc44ad/java/java/JavaParser.g4#L588

I reactivated the travis build and see the same thing there: https://travis-ci.org/vlingo/vlingo-schemata/builds/650400216#L7382. On CircleCI, the same schemata state built successfully 4d ago (https://app.circleci.com/github/vlingo/vlingo-schemata/pipelines/18533e9f-f705-4e03-baff-e74d0b6e6f2f/workflows/29a36593-bd09-485f-ba98-12c267759c95) and failed today with the same issue...

No, I thought we'd check validity/escape/sanitize content on the server side when the user saves content, as the request can come from our UI as well as from some other...

As an alternative (I haven't found it mvn central), you can pull it via jitpack: https://jitpack.io/#svzdvd/jaxb-lombok-plugin

As an alternative, we could use the getops.sh script providing a posix compliant parser for long options: https://gist.github.com/wwerner/31758b8083746eb285e7eb62b55e532e