feat(meta): decouple barrier collect and sync in global barrier manager #5724
Annotations
8 errors and 2 warnings
proto/stream_service.proto#L48
Previously present field "2" with name "status" on message "BarrierCompleteResponse" was deleted without reserving the name "status".
|
proto/stream_service.proto#L48
Previously present field "3" with name "create_mview_progress" on message "BarrierCompleteResponse" was deleted without reserving the name "create_mview_progress".
|
proto/stream_service.proto#L48
Previously present field "2" with name "status" on message "BarrierCompleteResponse" was deleted without reserving the number "2".
|
proto/stream_service.proto#L48
Previously present field "3" with name "create_mview_progress" on message "BarrierCompleteResponse" was deleted without reserving the number "3".
|
proto/stream_service.proto#L49
Field "1" with name "task_id" on message "BarrierCompleteResponse" changed option "json_name" from "requestId" to "taskId".
|
proto/stream_service.proto#L49
Field "1" with name "task_id" on message "BarrierCompleteResponse" changed type from "string" to "uint64". See https://developers.google.com/protocol-buffers/docs/proto3#updating for wire compatibility rules and https://developers.google.com/protocol-buffers/docs/proto3#json for JSON compatibility rules.
|
proto/stream_service.proto#L49
Field "1" on message "BarrierCompleteResponse" changed name from "request_id" to "task_id".
|
|
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
This job failed
Loading