feat(sql-backend): [PART 2] introduce metadata manager and adapt it in all RPC services, dashboard, metric etc · risingwavelabs/risingwave@856664a

Triggered via pull request January 2, 2024 06:04

yezizp2012

synchronize #14191

feat/metadata-mgr

Status Failure

Total duration 20s

Artifacts –

protobuf-breaking.yml

on: pull_request

10 errors and 1 warning

Previously present field "3" with name "version" on message "CreateDatabaseResponse" was deleted without reserving the number "3".

Previously present field "3" with name "version" on message "CreateSchemaResponse" was deleted without reserving the number "3".

Previously present field "3" with name "version" on message "CreateSourceResponse" was deleted without reserving the number "3".

Previously present field "3" with name "version" on message "CreateSinkResponse" was deleted without reserving the number "3".

Previously present field "3" with name "version" on message "CreateMaterializedViewResponse" was deleted without reserving the number "3".

Previously present field "3" with name "version" on message "CreateViewResponse" was deleted without reserving the number "3".

Previously present field "3" with name "version" on message "CreateTableResponse" was deleted without reserving the number "3".

Previously present field "3" with name "version" on message "CreateFunctionResponse" was deleted without reserving the number "3".

Previously present field "4" with name "version" on message "CreateIndexResponse" was deleted without reserving the number "4".

Previously present field "2" with name "version" on message "CreateConnectionResponse" was deleted without reserving the number "2".

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/