title: Dataflow with Go SDK failing with 'InvalidProtocolBufferException'
body: <p>We were previously running Beam 2.11.0 which started failing due to an apparent change in URN format. When I attempted to update and use the latest release (2.13.0) the pipeline started timing out, and the only seemingly relevant error that I could identify from the logs during testing was:</p>
  
  <p><code>org.apache.beam.vendor.grpc.v1p13p1.com.google.protobuf.InvalidProtocolBufferException: While parsing a protocol message, the input ended unexpectedly in the middle of a field. This could mean either that the input has been truncated or that an embedded message misreported its own length.</code></p>
  
  <p>To further test this, I attempted to use the wordcount example as provided in the Beam docs/repo here - <a href="https://beam.apache.org/get-started/wordcount-example/" rel="nofollow noreferrer">https://beam.apache.org/get-started/wordcount-example/</a> - But I got the same result. I'm not sure if this is a generic error or something to do with Dataflow. The pipelines seem to work when running via direct runner.</p>
  
  <p>Note: I have rebuilt our worker_harness_container_image with the latest version.</p>
  
  <p>I understand the Go SDK is not officially supported by Dataflow, but could anybody tell me if the error is something related to Dataflow or some other issue?</p>
  
  <p>PS: I've asked the question in Dataflow and Beam Slack channels but haven't had any response.</p>