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

Rollforward of commit 4162cc54ba0b128b616c0bd05b65bf9ad5e66f2e. #10592

Closed
wants to merge 2 commits into from

Conversation

Yannic
Copy link
Contributor

@Yannic Yannic commented Jan 15, 2020

proto_lang_toolchain: Add original sources of ProtoInfo to blacklistedProtos

This fixes the problem reported in #10588

Fixes #10484

@Yannic
Copy link
Contributor Author

Yannic commented Jan 15, 2020

cc @meteorcloudy

@meteorcloudy
Copy link
Member

@Yannic Thanks for the fix!
I'm now running a downstream test for this change at:
https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1353

Can you also add a test to prevent the regression?

@meteorcloudy
Copy link
Member

The downstream looks good!

@Yannic
Copy link
Contributor Author

Yannic commented Jan 15, 2020

@meteorcloudy
Copy link
Member

Perfect! I'll merge this PR

@bazel-io bazel-io closed this in 1821bd5 Jan 15, 2020
@Yannic Yannic deleted the fix_10484_take_2 branch March 11, 2020 10:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

proto_lang_toolchain and blacklisted_protos with ProtoInfo not propagated correctly
3 participants