-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regenerate protos using protoc 3.19.4 #5945
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: harupy <hkawamura0130@gmail.com>
Signed-off-by: harupy <hkawamura0130@gmail.com>
dbczumar
approved these changes
May 26, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks @harupy !
29 tasks
Signed-off-by: harupy <hkawamura0130@gmail.com>
Signed-off-by: harupy <hkawamura0130@gmail.com>
Signed-off-by: harupy <hkawamura0130@gmail.com>
Signed-off-by: harupy <hkawamura0130@gmail.com>
Signed-off-by: harupy <hkawamura0130@gmail.com>
Signed-off-by: harupy <hkawamura0130@gmail.com>
Signed-off-by: harupy <hkawamura0130@gmail.com>
Signed-off-by: harupy <hkawamura0130@gmail.com>
dbczumar
pushed a commit
that referenced
this pull request
May 26, 2022
* Regenerate protos Signed-off-by: harupy <hkawamura0130@gmail.com> * use 3.19.4 Signed-off-by: harupy <hkawamura0130@gmail.com> * upgrade protobuf Signed-off-by: harupy <hkawamura0130@gmail.com> * pin protobuf Signed-off-by: harupy <hkawamura0130@gmail.com> * change permission Signed-off-by: harupy <hkawamura0130@gmail.com> * sudo Signed-off-by: harupy <hkawamura0130@gmail.com> * use /tmp Signed-off-by: harupy <hkawamura0130@gmail.com> * fix permission Signed-off-by: harupy <hkawamura0130@gmail.com> * pin protobuf Signed-off-by: harupy <hkawamura0130@gmail.com> * remove redundant condition Signed-off-by: harupy <hkawamura0130@gmail.com> * set PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION Signed-off-by: harupy <hkawamura0130@gmail.com> * add protobuf requirement Signed-off-by: harupy <hkawamura0130@gmail.com>
29 tasks
Merged
29 tasks
30 tasks
4 tasks
postrational
pushed a commit
to postrational/mlflow
that referenced
this pull request
Jul 27, 2022
* Regenerate protos Signed-off-by: harupy <hkawamura0130@gmail.com> * use 3.19.4 Signed-off-by: harupy <hkawamura0130@gmail.com> * upgrade protobuf Signed-off-by: harupy <hkawamura0130@gmail.com> * pin protobuf Signed-off-by: harupy <hkawamura0130@gmail.com> * change permission Signed-off-by: harupy <hkawamura0130@gmail.com> * sudo Signed-off-by: harupy <hkawamura0130@gmail.com> * use /tmp Signed-off-by: harupy <hkawamura0130@gmail.com> * fix permission Signed-off-by: harupy <hkawamura0130@gmail.com> * pin protobuf Signed-off-by: harupy <hkawamura0130@gmail.com> * remove redundant condition Signed-off-by: harupy <hkawamura0130@gmail.com> * set PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION Signed-off-by: harupy <hkawamura0130@gmail.com> * add protobuf requirement Signed-off-by: harupy <hkawamura0130@gmail.com> Signed-off-by: Michal Karzynski <michal.karzynski@intel.com>
21 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: harupy hkawamura0130@gmail.com
Related Issues/PRs
Close #5949
What changes are proposed in this pull request?
Regenerate protos to fix the following error caused by a recent protobuf release:
How is this patch tested?
Existing tests
Does this PR change the documentation?
ci/circleci: build_doc
check. If it's successful, proceed to thenext step, otherwise fix it.
Details
on the right to open the job page of CircleCI.Artifacts
tab.docs/build/html/index.html
.Release Notes
Is this a user-facing change?
(Details in 1-2 sentences. You can just refer to another PR with a description if this PR is part of a larger change.)
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/artifacts
: Artifact stores and artifact loggingarea/build
: Build and test infrastructure for MLflowarea/docs
: MLflow documentation pagesarea/examples
: Example codearea/model-registry
: Model Registry service, APIs, and the fluent client calls for Model Registryarea/models
: MLmodel format, model serialization/deserialization, flavorsarea/projects
: MLproject format, project running backendsarea/scoring
: MLflow Model server, model deployment tools, Spark UDFsarea/server-infra
: MLflow Tracking server backendarea/tracking
: Tracking Service, tracking client APIs, autologgingInterface
area/uiux
: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/docker
: Docker use across MLflow's components, such as MLflow Projects and MLflow Modelsarea/sqlalchemy
: Use of SQLAlchemy in the Tracking Service or Model Registryarea/windows
: Windows supportLanguage
language/r
: R APIs and clientslanguage/java
: Java APIs and clientslanguage/new
: Proposals for new client languagesIntegrations
integrations/azure
: Azure and Azure ML integrationsintegrations/sagemaker
: SageMaker integrationsintegrations/databricks
: Databricks integrationsHow should the PR be classified in the release notes? Choose one:
rn/breaking-change
- The PR will be mentioned in the "Breaking Changes" sectionrn/none
- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/feature
- A new user-facing feature worth mentioning in the release notesrn/bug-fix
- A user-facing bug fix worth mentioning in the release notesrn/documentation
- A user-facing documentation change worth mentioning in the release notes