-
-
Notifications
You must be signed in to change notification settings - Fork 374
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
Pyright job is flaky and temporarily optional #1121
Labels
Meta
Issues regarding building, packaging, shipping, ...
Comments
Instead of commenting out the job dependency, you can use an action input to mark when it's okay for a job to fail FYI |
If you wanna open a PR, feel free. For me that was easier than reading docs. ..🤪 |
Looks like pyright is now really breaking as of presumably 1.1.309:
Volunteers? 😇🤓 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Presumably due to some hosting changes, nodeenv and by extension Pyright are regularly failing now.
I've marked it as optional for now, but would like to re-activate it ASAP.
Ref ekalinin/nodeenv#324
The text was updated successfully, but these errors were encountered: