search

salesforce / reactive-grpc

Reactive stubs for gRPC
BSD 3-Clause "New" or "Revised" License
833 stars 118 forks source link

Bazel demo does not compile #324

Open ubmarco opened 1 year ago

ubmarco commented 1 year ago

Building the Bazel demo https://github.com/salesforce/reactive-grpc/tree/master/demos/bazel is failing for me:

demos/bazel $ bazel build //src/main/java/com/salesforce/servicelibs/reactivegrpc:reactivegrpc_bin --incompatible_java_common_parameters=false

INFO: Analyzed target //src/main/java/com/salesforce/servicelibs/reactivegrpc:reactivegrpc_bin (89 packages loaded, 1579 targets configured).
INFO: Found 1 target...
ERROR: /home/qxg3568/.cache/bazel/_bazel_qxg3568/c82a11a5d733a2b470a92ea2a8a4d128/external/com_salesforce_servicelibs_reactive_grpc/common/reactive-grpc-common/BUILD.bazel:1:13: Building external/com_salesforce_servicelibs_reactive_grpc/common/reactive-grpc-common/libreactive-grpc-common.jar (11 source files) failed: (Exit 1): java failed: error executing command (from target @com_salesforce_servicelibs_reactive_grpc//common/reactive-grpc-common:reactive-grpc-common) external/remotejdk11_linux/bin/java -XX:-CompactStrings '--add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.main=ALL-UNNAMED' ... (remaining 18 arguments skipped)
external/com_salesforce_servicelibs_reactive_grpc/common/reactive-grpc-common/src/main/java/com/salesforce/reactivegrpc/common/AbstractSubscriberAndServerProducer.java:30: error: cannot find symbol
        ((ServerCallStreamObserver<?>) downstream).setOnCloseHandler(AbstractSubscriberAndServerProducer.super::cancel);
                                                  ^
  symbol:   method setOnCloseHandler(AbstractSu[...]ancel)
  location: class ServerCallStreamObserver<CAP#1>
  where CAP#1 is a fresh type-variable:
    CAP#1 extends Object from capture of ?
Target //src/main/java/com/salesforce/servicelibs/reactivegrpc:reactivegrpc_bin failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 16.277s, Critical Path: 10.29s
INFO: 92 processes: 15 internal, 71 linux-sandbox, 6 worker.
FAILED: Build did NOT complete successfully

Is that an issue on my end?

rmichela commented 1 year ago

Likely, the bazel demo is broken. Bazel is not my specialty.