-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
chore: update eslint-plugin-import-x #29088
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
Conversation
import-x/resolver-next
import-x/resolver-next
Why |
Thanks @JounQin. generator-jhipster/lib/eslint/base.js Line 13 in fa9eb9b
We apply selected rules that have auto fix to generated code. Eslint logic is here: |
The segmentation fault happens on the thread teardown (piscina pool destroy):
|
I think it could be related? |
No, #29070 |
@mshima By the way, why |
|
I believe this should be related to cc @Brooooooklyn Does |
@mshima I just upgraded |
@mshima Wow, seems passing... |
import-x/resolver-next
@JounQin thanks for your help. |
Related un-ts/eslint-plugin-import-x#266
cc @mshima
Please make sure the below checklist is followed for Pull Requests.
When you are still working on the PR, consider converting it to Draft (below reviewers) and adding
skip-ci
label, you can still see CI build result at your branch.