Skip to content
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

Fix nightly Rust build of prost #20041

Merged
merged 1 commit into from
Jun 20, 2023

Conversation

def-
Copy link
Contributor

@def- def- commented Jun 20, 2023

Uses MaterializeInc/prost#4

error: failed to load source for dependency `prost`

Caused by:
  Unable to update https://github.com/MaterializeInc/prost#17cc373b

Caused by:
  failed to update submodule `prost-build/third-party/protobuf`

Caused by:
  failed to parse url for submodule `prost-build/third-party/protobuf`: `git@github.com:protocolbuffers/protobuf`

Caused by:
  relative URL without a base

Motivation

  • This PR fixes a previously unreported bug.

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered.
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
  • This PR includes the following user-facing behavior changes:

@def- def- requested review from benesch and teskje June 20, 2023 13:37
@def-
Copy link
Contributor Author

def- commented Jun 20, 2023

I think have to land MaterializeInc/prost#4 first.

@benesch
Copy link
Member

benesch commented Jun 20, 2023 via email

@def- def- force-pushed the pr-fix-nightly-build-prost branch from 43ffd47 to d7449ca Compare June 20, 2023 15:18
@def-
Copy link
Contributor Author

def- commented Jun 20, 2023

Seems to work, done.

Copy link
Member

@benesch benesch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome, thank you!

Copy link
Contributor

@teskje teskje left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@def- def- force-pushed the pr-fix-nightly-build-prost branch 2 times, most recently from 36603ae to bc0d5c3 Compare June 20, 2023 15:35
@def- def- requested a review from a team as a code owner June 20, 2023 15:35
@def- def- requested a review from a team June 20, 2023 15:35
@def-
Copy link
Contributor Author

def- commented Jun 20, 2023

Actually my bad. prost v0.11.9 did not contain tokio-rs/prost#833, so we still have the same problem with prettyplease. I'm guessing prost v0.12.0 needs to be released to fix that first.

@def- def- force-pushed the pr-fix-nightly-build-prost branch from bc0d5c3 to 43ffd47 Compare June 20, 2023 15:46
@benesch
Copy link
Member

benesch commented Jun 20, 2023

I think just allow the duplicate dependency in deny.toml. Seems better than having to manage a bunch of patches for this.

by going back to upstream prost version

error: failed to load source for dependency `prost`

Caused by:
  Unable to update https://github.com/MaterializeInc/prost#17cc373b

Caused by:
  failed to update submodule `prost-build/third-party/protobuf`

Caused by:
  failed to parse url for submodule `prost-build/third-party/protobuf`: `git@github.com:protocolbuffers/protobuf`

Caused by:
  relative URL without a base
@def- def- force-pushed the pr-fix-nightly-build-prost branch from 43ffd47 to 6f264c1 Compare June 20, 2023 16:00
@def- def- enabled auto-merge June 20, 2023 16:19
@def- def- merged commit 37f5f85 into MaterializeInc:main Jun 20, 2023
@def- def- deleted the pr-fix-nightly-build-prost branch June 20, 2023 17:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants