bufbuild / buf

The best way of working with Protocol Buffers.
https://buf.build
Apache License 2.0
9.22k stars 279 forks source link

remote plugin fail #3488

Closed mingzaily closed 4 days ago

mingzaily commented 4 days ago

GitHub repository with your minimal reproducible example (do not leave this field blank or fill out this field with "github.com/bufbuild/buf" or we will automatically close your issue, see the instructions above!)

No response

What's up?

Everything was normal until today, but an error was reported today

Failure: unimplemented: unary response has zero messages for https://buf.build/buf.alpha.registry.v1alpha1.CodeGenerationService/GenerateCode
This version of the buf CLI may require APIs that have not yet been deployed to https://buf.build
To resolve this failure, you can either:
- Try using an older version of the buf CLI
- Contact the site admin for https://buf.build to upgrade the instance

Our yaml file

version: v1
managed:
  enabled: true

plugins:
  - plugin: buf.build/protocolbuffers/go:v1.33.0
    out: apis-go
    opt: paths=source_relative
  - plugin: buf.build/grpc/go:v1.4.0 
    out: apis-go
    opt: paths=source_relative,require_unimplemented_servers=false
  - plugin: buf.build/bufbuild/validate-go:v1.0.4
    out: apis-go
    opt: paths=source_relative
  - plugin: go-http # kartos local plugin
    out: apis-go
    opt:
      - paths=source_relative
ddeath commented 4 days ago

We are getting timeouts as well when trying to generate code.

DEBUG   buf.alpha.registry.v1alpha1.CodeGenerationService/GenerateCode  {"duration": "1m59.96543675s", "status": "Error", "net.peer.name": "buf.build", "rpc.system": "connect_rpc", "rpc.service": "buf.alpha.registry.v1alpha1.CodeGenerationService", "rpc.method": "GenerateCode", "rpc.connect_rpc.error_code": "deadline_exceeded", "message.type": "SENT", "message.id": 1, "message.uncompressed_size": 296111, "message.type": "RECEIVED", "message.id": 1, "message.uncompressed_size": 0}
DEBUG   command {"duration": "2m0.005140417s", "status": "Unset"}
Failure: context deadline exceeded

Why is code generation depending on CodeGenerationService? I would expect that it happens locally on machine so if I have dependencies cached locally it will work even without connection 🤔

mingzaily commented 4 days ago

We are getting timeouts as well when trying to generate code.我们在尝试生成代码时也遇到了超时问题。

DEBUG buf.alpha.registry.v1alpha1.CodeGenerationService/GenerateCode  {"duration": "1m59.96543675s", "status": "Error", "net.peer.name": "buf.build", "rpc.system": "connect_rpc", "rpc.service": "buf.alpha.registry.v1alpha1.CodeGenerationService", "rpc.method": "GenerateCode", "rpc.connect_rpc.error_code": "deadline_exceeded", "message.type": "SENT", "message.id": 1, "message.uncompressed_size": 296111, "message.type": "RECEIVED", "message.id": 1, "message.uncompressed_size": 0}
DEBUG command {"duration": "2m0.005140417s", "status": "Unset"}
Failure: context deadline exceeded

Why is code generation depending on CodeGenerationService? I would expect that it happens locally on machine so if I have dependencies cached locally it will work even without connection 🤔为什么代码生成依赖于 CodeGenerationService?我本以为它会在本地机器上执行,如果我已经本地缓存了依赖项,即使没有连接也能工作 🤔

Yes, same question, even with the agent In debug mode

DEBUG   buf.alpha.registry.v1alpha1.CodeGenerationService/GenerateCode  {"duration": "7.778765709s", "status": "Unset", "net.peer.name": "buf.build", "rpc.system": "connect_rpc", "rpc.service": "buf.alpha.registry.v1alpha1.CodeGenerationService", "rpc.method": "GenerateCode", "message.type": "SENT", "message.id": 1, "message.uncompressed_size": 2566174, "message.type": "RECEIVED", "message.id": 1, "message.uncompressed_size": 26110715}
DEBUG   command {"duration": "8.135314125s", "status": "Unset"}
ddeath commented 4 days ago

Buf people confirmed on slack that they see the issue.

we are aware of the issue and working on determining the cause at the moment, will update the status page.

Juneezee commented 4 days ago

We are experiencing the same issue too.

buf generate --debug
DEBUG   buffetch termination found  {"curDirPath": "home/jun/Desktop/tux", "path": "home/jun/Desktop/tux"}
DEBUG   buffetch termination found  {"curDirPath": ".", "path": "."}
DEBUG   targeting workspace based on v2 buf.yaml    {"subDirPath": "."}
DEBUG   github.com/bufbuild/buf/private/buf/bufworkspace.(*workspaceProvider).getWorkspaceForBucketBufYAMLV2    {"duration": "22.419µs"}
DEBUG   github.com/bufbuild/buf/private/buf/bufctl.(*controller).getWorkspaceForSourceRef   {"duration": "385.385µs"}
DEBUG   module data store dir read write bucket {"moduleFullName": "buf.build/googleapis/googleapis", "commitID": "e7f8d366f5264595bcc4cd4139af9973", "dirPath": "b5/buf.build/googleapis/googleapis/e7f8d366f5264595bcc4cd4139af9973"}
DEBUG   module data store get module.yaml   {"moduleFullName": "buf.build/googleapis/googleapis", "commitID": "e7f8d366f5264595bcc4cd4139af9973", "found": true}
DEBUG   github.com/bufbuild/buf/private/bufpkg/bufimage.BuildImage  {"duration": "38.747038ms"}
Failure: the server hosted at that remote is unavailable
mingzaily commented 4 days ago

Buf people confirmed on slack that they see the issue.

we are aware of the issue and working on determining the cause at the moment, will update the status page.

Can you provide a slack link? I want to follow. Thanks!

ddeath commented 4 days ago

Can you provide a slack link? I want to follow. Thanks!

https://bufbuild.slack.com/archives/CRZ680FUH/p1732249389249809

unmultimedio commented 4 days ago

Thank you all for the report. We have implemented a fix, the system looks healthy now, we keep monitoring the code generation service.

Here is a link to the incident in our status page: https://www.bufstatus.com/cm3s95tid00cdej4ouynppm6s