Sergio Regueira

He subido el parche mediante pull request (https://github.com/gallir/Meneame/pull/106).

Hello everybody, After reading this issue, I tried to query a table with identifiers stored in `INT64` columns with `wrapIntegers` property set to `true`, but it loses precision even using...

Related issue: https://github.com/googleapis/google-cloud-node/issues/2438

@murgatroid99 the problem is gRPC library does not reconnect after that error, so applications stop sending logs to Stackdriver. When this happens, we have to replace the affected instance with...

@murgatroid99 @nicolasnoble I am sorry for the delay. I was a bit busy these days. The same day you asked me for more information, I enabled gRPC debugging setting some...

More examples where it does not reconnect: ``` I0118 20:49:56.469767934 6 tcp_custom.cc:128] TCP:0x6714db57150 call_cb 0x6714dbdfb78 0x15de0f0a69d0:0x6714dbdfb20 I0118 20:49:56.469810638 6 tcp_custom.cc:132] read: error={"created":"@1547844596.469749556","description":"TCP Read failed","file":"../deps/grpc/src/core/lib/iomgr/tcp_uv.cc","file_line":73,"grpc_status":14,"os_error":"connection reset by peer"} I0118 20:49:56.469885894 6...

@murgatroid99 I mean the application continues working properly but Stackdriver does not process more logs of the affected instance (including gRPC traces). Logs generated automatically (ie. `appengine.googleapis.com/request_log`) are not interrupted....

@murgatroid99 On the one hand, our application logs are sent to Stackdriver via `nodejs-logging` (that uses internally gRPC) in a structured way (using `LogEntry.jsonPayload` object). On the other hand, gRPC...

Good news! I have updated `@google-cloud/logging` package to `4.3.0` version one week ago and no more errors detected on integration, staging nor production environment since then. Thanks everyone :) P.S:...