Improve Errors for Transitive Rules
See original GitHub issueDescription of the feature request:
improve errors in transitive rules
what we get:
ERROR: /usr/local/google/home/aryehh/Development/cloud-spanner-emulator/binaries/BUILD:23:10: While resolving toolchains for target //binaries:emulator_main: invalid registered toolchain '@rules_foreign_cc//tools/build_defs/shell_toolchain/toolchains:linux_commands': error loading package '@rules_foreign_cc//tools/build_defs/shell_toolchain/toolchains': at /usr/local/google/home/aryehh/.cache/bazel/_bazel_aryehh/432487528c3e0374d8bae32ea74d9eb8/external/rules_foreign_cc/tools/build_defs/shell_toolchain/toolchains/defs.bzl:6:6: at /usr/local/google/home/aryehh/.cache/bazel/_bazel_aryehh/432487528c3e0374d8bae32ea74d9eb8/external/commands_overloads/toolchain_data_defs.bzl:3:6: compilation of module 'windows_commands.bzl' failed
what might be more ideal:
ERROR: /usr/local/google/home/aryehh/Development/cloud-spanner-emulator/binaries/BUILD:23:10: While resolving toolchains for target //binaries:emulator_main: invalid registered toolchain
'@rules_foreign_cc//tools/build_defs/shell_toolchain/toolchains:linux_commands': error loading package
'@rules_foreign_cc//tools/build_defs/shell_toolchain/toolchains':
at /usr/local/google/home/aryehh/.cache/bazel/_bazel_aryehh/432487528c3e0374d8bae32ea74d9eb8/external/rules_foreign_cc/tools/build_defs/shell_toolchain/toolchains/defs.bzl:6:6:
at /usr/local/google/home/aryehh/.cache/bazel/_bazel_aryehh/432487528c3e0374d8bae32ea74d9eb8/external/commands_overloads/toolchain_data_defs.bzl:3:6: compilation of module 'windows_commands.bzl' failed
or something similar
What underlying problem are you trying to solve with this feature?
Understanding the dependency graph when an error in a rule happens
Which operating system are you running Bazel on?
glinux
What is the output of bazel info release
?
release 5.2.0
If bazel info release
returns development version
or (@non-git)
, tell us how you built Bazel.
No response
What’s the output of git remote get-url origin; git rev-parse master; git rev-parse HEAD
?
No response
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response
Issue Analytics
- State:
- Created a year ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
15 Rules for Spotting Errors in English || AMCAT Verbal Ability
Subscribe here - https://goo.gl/wKmO6Z☛Facebook - https://www.facebook.com/talentsprint/?fref=ts☛Visit Our WebSite ...
Read more >Azure SQL Database - Working with transient errors
Learn how to troubleshoot, diagnose, and prevent a SQL connection error or transient error when connecting to Azure SQL Database, Azure SQL ...
Read more >Error Spotting Rules Based on Verbs - BankExamsToday
Some other examples of transitive verbs are address, borrow, bring, discuss, raise, offer, pay, write, promise, and have.
Read more >Better management of transitive dependencies and conflicts
Sometimes, we want more control, and do not want any conflict resolution to happen. Instead, we would like an error to be reported...
Read more >Empowering English Teachers to Grapple with Errors in ...
It aims to provide a practical guide in developing teachers' skills in identifying and classifying students' errors, and in explaining grammatical rules.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@sgowroji I think that this issue is still valid. It isn’t tied to a particular project, it’s just about better error messages. @gregestren who I think has an ongoing project for more beautiful error messages.
Closing as it is stale. Please reach us back if you still looking resolution for the above request or open a new issue adding the above as reference.