We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
npm run lint
Sometimes CI Lint step fails.
npm run lint is invoked (on the repo-root level). This command never finishes. The output is:
> lint > npm --workspaces --if-present run lint > enso-ide-desktop@1.0.0 lint > npm run --workspace=enso-gui2 compile-server && npm run lint-only > enso-gui2@0.1.0 compile-server > tsc -p tsconfig.server.json > enso-ide-desktop@1.0.0 lint-only > eslint . > enso-gui2@0.1.0 lint > eslint .
This has happened at least twice on CI:
Both times with the same output, suggesting that it is the enso-gui2 linting specifically that causes deadlock.
enso-gui2
The text was updated successfully, but these errors were encountered:
Another instance of this problem here https://github.com/enso-org/enso/actions/runs/7743955599/job/21116570129?pr=8764
GitHubFix Truffle invariants for Nothing with a warning · enso-org/enso@ad5ec40Hybrid visual and textual functional programming. Contribute to enso-org/enso development by creating an account on GitHub.
Sorry, something went wrong.
Seems to be fixed by #8947 as I don't see those errors since a week.
farmaazon
No branches or pull requests
Sometimes CI Lint step fails.
npm run lint
is invoked (on the repo-root level). This command never finishes. The output is:This has happened at least twice on CI:
Both times with the same output, suggesting that it is the
enso-gui2
linting specifically that causes deadlock.The text was updated successfully, but these errors were encountered: