sdoeringNew

Glad to here it. 👍 Unfortunately the PR is still not approved.

I'm interested in this feature as well. I'm also behind a corporate proxy only having a self signed certificate. I could imagine adding an additional configuration: true And then adding...

> If it is just one spec, what is stopping you from just setting it to CONCURRENT? The specifications - those features can run concurrently - may not run concurrently.

Just as information. With four threads and twelve blocks I get around 20H/s on my Jetson with the 5V/2A USB power connector. It takes ~8Wh in 90min.

Is referencing to a different path a thing? By looking at OpenAPIDeserializer.java it isn't. private Parameter getParameterDefinition(Parameter parameter) { if (parameter.get$ref() == null) { return parameter; } Object parameterSchemaName =...

On a sidenote... The Swagger Editor handles this referencing without any problems and certainly gives no warnings.

You can't find it there anymore. Look at: https://github.com/fge/json-schema-validator It redirects to the new maintainer: https://github.com/java-json-tools/json-schema-validator And you can see fge's last update on the README.md looking for a new...

I solved it by dismissing the ``protocVersion`` property in the plugin and start using the ``protocArtifact`` property. com.google.protobuf:protoc:${protobuf.version} That seems to be a common issue. See: https://github.com/os72/protoc-jar-maven-plugin/issues/124 https://github.com/os72/protoc-jar-maven-plugin/issues/131

In the newest versions the workaround with the developer mode is not working anymore. First install an older version of the "Yandex Browser with Protect", add uBlock Origin as described...

On further investigation the Java garbage collection is not the cause for the high latency.