František Hartman
František Hartman
The job @nfrankel was submitting incorrectly used `Jet.newJetClient()` instead of `Jet.bootstrappedInstance()`. The `-f` option works as expected, but we should consider improving the documentation to make it clearer that the...
Hi @wfhartford , thanks for reporting this. There is a note in the documentation for the observable sink: > Jet internally uses Hazelcast's Ringbuffer to create a temporary buffer to...
Yes, it should be there to distinguish call homes between Jet jar from maven, from tar/zip distribution and from docker. ``` $ cat hazelcast-jet-4.4-SNAPSHOT/lib/hazelcast-download.properties hazelcastDownloadId=distribution $ docker run hazelcast/hazelcast-jet:latest-snapshot cat...
Options discussed: - have the file with the correct value in `hazelcast-jet` jar - I don't like this as we would have 3 different jars - one in maven central,...
This looks like a compatibility issue of Mockito (and underlying ByteBuddy library) and OpenJ9. This is a similar, but not identical, issue https://github.com/mockito/mockito/issues/1899. It suggests it could be caused by...
The root cause of the exception slightly differs on the updated version of ibm jdk: ``` Caused by: com.sun.tools.attach.AttachNotSupportedException: target 147145 not found at com.ibm.tools.attach.attacher.OpenJ9VirtualMachine.attachTargetImpl(OpenJ9VirtualMachine.java:150) at com.ibm.tools.attach.attacher.OpenJ9VirtualMachine.lambda$attachTarget$1(OpenJ9VirtualMachine.java:128) at com.ibm.tools.attach.attacher.OpenJ9VirtualMachine$$Lambda$37/0000000078EFDAF0.run(Unknown Source)...
I wonder if we should mark these vulnerabilities as false positives - the reason is that libraries like `hadoop-yarn-common` are used both in server distribution of hadoop, where they serve...
Similarly the `add-third-party` is not thread safe. @tchemit Could it be made thread-safe? Should I create a separate issue for that? Are there any changes needed to the plugin? I...
Hi, we are occasionally facing the #354 issue with the plugin when running a parallel build. I have looked into @Stephan202's fix and I think additional modifications are needed: -...
run-lab-run