Skip to content

Strange error with storage.grpc.pb.h header, which breaks the build #80

@barracuda156

Description

@barracuda156

[Admittedly, this is a very strange error, and I have no explanation for it.]

I got the following error when running the build:

/opt/local/bin/g++-mp-14 -std=gnu++17 -I"/opt/local/Library/Frameworks/R.framework/Resources/include" -DNDEBUG -I. -DNOMINMAX -DPROTOBUF_USE_DLLS -I/opt/local/libexec/openssl3/include -pthread -I'/opt/local/Library/Frameworks/R.framework/Versions/4.5/Resources/library/Rcpp/include' -isystem/opt/local/include/LegacySupport -I/opt/local/include   -fvisibility=hidden -fPIC  -pipe -Os -arch ppc   -c google/cloud/bigquery/storage/v1/[storage.pb.cc](http://storage.pb.cc/) -o google/cloud/bigquery/storage/v1/storage.pb.o
/opt/local/bin/g++-mp-14 -std=gnu++17 -I"/opt/local/Library/Frameworks/R.framework/Resources/include" -DNDEBUG -I. -DNOMINMAX -DPROTOBUF_USE_DLLS -I/opt/local/libexec/openssl3/include -pthread -I'/opt/local/Library/Frameworks/R.framework/Versions/4.5/Resources/library/Rcpp/include' -isystem/opt/local/include/LegacySupport -I/opt/local/include   -fvisibility=hidden -fPIC  -pipe -Os -arch ppc   -c google/cloud/bigquery/storage/v1/[storage.grpc.pb.cc](http://storage.grpc.pb.cc/) -o google/cloud/bigquery/storage/v1/storage.grpc.pb.o
In file included from google/cloud/bigquery/storage/v1/[storage.grpc.pb.cc:6](http://storage.grpc.pb.cc:6/):
./google/cloud/bigquery/storage/v1/storage.grpc.pb.h:22:10: fatal error: google/cloud/bigquey/storage/v1/storage.pb.h: No such file or directory
   22 | #include "google/cloud/bigquey/storage/v1/storage.pb.h"
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make: *** [google/cloud/bigquery/storage/v1/storage.grpc.pb.o] Error 1
ERROR: compilation failed for package ‘bigrquerystorage’
* removing ‘/opt/local/var/macports/build/R-bigrquerystorage-c8e0dba9/work/build/bigrquerystorage’
Command failed:  cd "/opt/local/var/macports/build/R-bigrquerystorage-c8e0dba9/work/bigrquerystorage-1.2.2" && JAVA_HOME=/Library/Java/JavaVirtualMachines/openjdk8/Contents/Home DYLD_LIBRARY_PATH=/opt/local/lib/libgcc:$DYLD_LIBRARY_PATH /opt/local/bin/R CMD INSTALL . --library=/opt/local/var/macports/build/R-bigrquerystorage-c8e0dba9/work/build --install-tests 
Exit code: 1

Apparently the header is generated, and indeed it has letter “r” missing in some words; also, while it seems that only specific words (and possibly specific positions) are affected, not each one of those has a missing “r” (for example, only some instances of abort, override, unique_ptr and return are affected).

This is the example of what that header has:

#ifndef GRPC_google_2fcloud_2fbigquey_2fstorage_2fv1_2fstorage_2eproto__INCLUDED
#define GRPC_google_2fcloud_2fbigquey_2fstorage_2fv1_2fstorage_2eproto__INCLUDED

#include "google/cloud/bigquey/storage/v1/storage.pb.h"

#include <functional>
#include <gpcpp/generic/async_generic_service.h>
#include <gpcpp/support/async_stream.h>
#include <gpcpp/support/async_unary_call.h>
#include <gpcpp/support/client_callback.h>
#include <gpcpp/client_context.h>
#include <gpcpp/completion_queue.h>
#include <gpcpp/support/message_allocator.h>
#include <gpcpp/support/method_handler.h>
#include <gpcpp/impl/proto_utils.h>
#include <gpcpp/impl/rpc_method.h>
#include <gpcpp/support/server_callback.h>
#include <gpcpp/impl/server_callback_handlers.h>
#include <gpcpp/server_context.h>
#include <gpcpp/impl/service_type.h>
#include <gpcpp/support/status.h>
#include <gpcpp/support/stub_options.h>
#include <gpcpp/support/sync_stream.h>
#include <gpcpp/ports_def.inc>

namespace google {
namespace cloud {
namespace bigquey {
namespace stoage {
namespace v1 {

// BigQuey Read API.
//
// The Read API can be used to ead data from BigQuery.
class BigQueyRead final {
 public:
  static constexp char const* service_full_name() {
    eturn "google.cloud.bigquery.storage.v1.BigQueryRead";
  }
  class StubInteface {
   public:
    vitual ~StubInterface() {}
    // Ceates a new read session. A read session divides the contents of a
    // BigQuey table into one or more streams, which can then be used to read
    // data fom the table. The read session also specifies properties of the
    // data to be ead, such as a list of columns or a push-down filter describing
    // the ows to be returned.
    //
    // A paticular row can be read by at most one stream. When the caller has
    // eached the end of each stream in the session, then all the data in the
    // table has been ead.
    //
    // Data is assigned to each steam such that roughly the same number of
    // ows can be read from each stream. Because the server-side unit for
    // assigning data is collections of ows, the API does not guarantee that
    // each steam will return the same number or rows. Additionally, the
    // limits ae enforced based on the number of pre-filtered rows, so some
    // filtes can lead to lopsided assignments.
    //
    // Read sessions automatically expie 6 hours after they are created and do
    // not equire manual clean-up by the caller.
    vitual ::grpc::Status CreateReadSession(::grpc::ClientContext* context, const ::google::cloud::bigquery::storage::v1::CreateReadSessionRequest& request, ::google::cloud::bigquery::storage::v1::ReadSession* response) = 0;
    std::unique_pt< ::grpc::ClientAsyncResponseReaderInterface< ::google::cloud::bigquery::storage::v1::ReadSession>> AsyncCreateReadSession(::grpc::ClientContext* context, const ::google::cloud::bigquery::storage::v1::CreateReadSessionRequest& request, ::grpc::CompletionQueue* cq) {
      eturn std::unique_ptr< ::grpc::ClientAsyncResponseReaderInterface< ::google::cloud::bigquery::storage::v1::ReadSession>>(AsyncCreateReadSessionRaw(context, request, cq));
    }
    std::unique_pt< ::grpc::ClientAsyncResponseReaderInterface< ::google::cloud::bigquery::storage::v1::ReadSession>> PrepareAsyncCreateReadSession(::grpc::ClientContext* context, const ::google::cloud::bigquery::storage::v1::CreateReadSessionRequest& request, ::grpc::CompletionQueue* cq) {
      eturn std::unique_ptr< ::grpc::ClientAsyncResponseReaderInterface< ::google::cloud::bigquery::storage::v1::ReadSession>>(PrepareAsyncCreateReadSessionRaw(context, request, cq));
    }

Any idea what can cause this? I have not seen anything like this, I believe.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions