Various updates build_file_generation example - #869
Conversation
6099634 to
a80dc3c
Compare
e109334 to
38b355d
Compare
be0739e to
bc9c36f
Compare
|
@alexeagle @f0rmiga @rickeylev PTAL |
6201f9b to
47a04ae
Compare
|
@f0rmiga I have made the updates you requested and reformatted the example code. I am hitting a weird thing though. $ bazel run //:gazelle -- update
INFO: Analyzed target //:gazelle (1 packages loaded, 2 targets configured).
INFO: Found 1 target...
Target //:gazelle up-to-date:
bazel-bin/gazelle-runner.bash
bazel-bin/gazelle
INFO: Elapsed time: 3.373s, Critical Path: 0.04s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
INFO: Build completed successfully, 1 total action
gazelle: ERROR: failed to validate dependencies for target "@build_file_generation_example//random_number_generator:random_number_generator_test": "generate_random_number" at line 16 from "random_number_generator/__test__.py" is an invalid dependency: possible solutions:
1. Add it as a dependency in the requirements.txt file.
2. Instruct Gazelle to resolve to a known dependency using the gazelle:resolve directive.
3. Ignore it with a comment '# gazelle:ignore generate_random_number' in the Python fileBut unit test will run and is working fine. The dependencies are not wrong. Thoughts? |
|
Add an |
This is not working. Let me know if you have any ideas. |
Updating the WORKSPACE file and BUILD file inline documentation. Added new code and new directories for example. Added new unit test for example. Added license headers.
14dff43 to
b13e4cd
Compare
- updating gazelle version to 0.28 - updating go version to 1.19.4
- added requirements_windows.txt from running //:requirements.update on windows - modified WORKSPACE and BUILD files to include different requirements.update when running the build on Windows
ec32d7c to
9adbc08
Compare
|
|
||
| @generated by rules_python pip_parse repository rule | ||
| from //:requirements.txt | ||
| from @//:requirements.txt |
There was a problem hiding this comment.
I had to do update this to get CI to pass
There was a problem hiding this comment.
That is spooky that our CI uses a floating version of bazel rather than what's pinned in our .bazelversion file - I think we ought to fix that along with updating that golden file.
|
@alexeagle this got log jammed on @f0rmiga review which I addressed. Any ideas? |
This PR covers various updates and addition to the example. I am writing a python tutorial much like the go tutorial.
Updating the WORKSPACE file and BUILD file inline documentation.
Added new source code
Added new unit test