Amar3tto commented on issue #33786: URL: https://github.com/apache/beam/issues/33786#issuecomment-2753731787
> The workers are failing with error: > > ``` > java.lang.NoSuchMethodError: 'boolean org.apache.beam.sdk.fn.data.BeamFnDataInboundObserver.multiplexElements(org.apache.beam.model.fnexecution.v1.BeamFnApi$Elements)' > at org.apache.beam.fn.harness.control.ProcessBundleHandler.processBundle(ProcessBundleHandler.java:528) > at org.apache.beam.fn.harness.control.BeamFnControlClient.delegateOnInstructionRequestType(BeamFnControlClient.java:150) > at org.apache.beam.fn.harness.control.BeamFnControlClient$InboundObserver.lambda$onNext$0(BeamFnControlClient.java:115) > at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at org.apache.beam.sdk.util.UnboundedScheduledExecutorService$ScheduledFutureTask.run(UnboundedScheduledExecutorService.java:163) > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) > at java.base/java.lang.Thread.run(Thread.java:840) > ``` > > My PR did change the signature of that method. However it's unclear why it is attempting to call the previous version from ProcessBundleHandler. Is there something odd about the jar setup in this test causing that? I think we just need to upload and then bump dataflow java container version, as it is currently at March 12th: `ext.dataflowFnapiContainerVersion = 'beam-master-20250312'` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@beam.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
