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.

Sign up for GitHub

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

Jump to bottom

Consider patching better Stardoc error messages into LTS 4.0.0 #13077

Closed
brandjon opened this issue Feb 20, 2021 · 1 comment
Closed

Consider patching better Stardoc error messages into LTS 4.0.0 #13077

brandjon opened this issue Feb 20, 2021 · 1 comment
Labels
P2 We'll consider working on this in future. (Assignee optional) team-Starlark-Integration Issues involving Bazel's integration with Starlark, excluding builtin symbols type: bug

Comments

@brandjon
Copy link
Member

See bazelbuild/stardoc#92 for a motivating case: Users are getting Stardoc failures with no actionable information while using an LTS release.
@brandjon brandjon added type: bug P2 We'll consider working on this in future. (Assignee optional) team-Starlark-Integration Issues involving Bazel's integration with Starlark, excluding builtin symbols labels Feb 20, 2021
@brandjon brandjon mentioned this issue Feb 20, 2021
Open
@brandjon
Copy link
Member Author

brandjon commented Nov 2, 2022

This wasn't done and it seems moot now that we're just days shy of releasing the second LTS after 4.0.

@brandjon brandjon closed this as not planned Won't fix, can't repro, duplicate, stale Nov 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
P2 We'll consider working on this in future. (Assignee optional) team-Starlark-Integration Issues involving Bazel's integration with Starlark, excluding builtin symbols type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@brandjon