Skip to content

+ operator on a depset is forbidden #484

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

Merged
merged 1 commit into from
Apr 24, 2018
Merged

Conversation

cushon
Copy link
Contributor

@cushon cushon commented Apr 24, 2018

Fixes:

ERROR: test/proto/BUILD:36:1: in scala_proto_srcjar rule //test/proto:test_proto_java_conversions_srcjar:
Traceback (most recent call last):
	File "test/proto/BUILD", line 36
		scala_proto_srcjar(name = 'test_proto_java_conversions_srcjar')
	File "scala_proto/scala_proto.bzl", line 332, in _gen_proto_srcjar_impl
		transitive_proto_paths += target.proto.transitive_proto_path
`+` operator on a depset is forbidden. See https://docs.bazel.build/versions/master/skylark/depsets.html for recommendations. Use --incompatible_depset_union=false to temporarily disable this check.

See also #480

Fixes:

ERROR: test/proto/BUILD:36:1: in scala_proto_srcjar rule //test/proto:test_proto_java_conversions_srcjar:
Traceback (most recent call last):
	File "test/proto/BUILD", line 36
		scala_proto_srcjar(name = 'test_proto_java_conversions_srcjar')
	File "scala_proto/scala_proto.bzl", line 332, in _gen_proto_srcjar_impl
		transitive_proto_paths += target.proto.transitive_proto_path
`+` operator on a depset is forbidden. See https://docs.bazel.build/versions/master/skylark/depsets.html for recommendations. Use --incompatible_depset_union=false to temporarily disable this check.

See also bazel-contrib#480
@johnynek
Copy link
Contributor

lgtm

confused why our test with --all_incompatible_changes didn't catch this.

@cushon
Copy link
Contributor Author

cushon commented Apr 24, 2018

confused why our test with --all_incompatible_changes didn't catch this.

That's how I noticed it, but I was testing with 0.12. Are you still using 0.11 because of the change to strict deps in 0.12?

@johnynek
Copy link
Contributor

we are still using 0.11 because the PR to bump to 0.12 failed CI: #481 and no one has diagnosed/repaired it AFAIK.

@cushon
Copy link
Contributor Author

cushon commented Apr 24, 2018

Makes sense. This is the only issue I saw with 0.12 related to --all_incompatible_changes, so I think it's worth fixing even though it isn't sufficient to get 0.12 working.

@johnynek johnynek merged commit bcc85cb into bazel-contrib:master Apr 24, 2018
@johnynek
Copy link
Contributor

thanks!

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.

3 participants