-
-
Notifications
You must be signed in to change notification settings - Fork 477
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
linter: 0.13.0 is hanging with --import-plugin
(or taking more than 5 minutes)
#7406
Comments
--import-plugin
(or taking more than 5 minutes)--import-plugin
(or taking more than 5 minutes)
is this a regression? does it work on older versions? |
Yes. 0.12.0 runs as expected for me. Sorry, forgot to put that into OP. Added it in now. |
got it, thanks. do you have a repo i can repro this on? |
I unfortunately don't. I'm seeing this in our massive monorepo and I wouldn't know where to start with figuring out with deconstructing the matrix of possibilities that could be making this happen. I was hoping there was something that made sense for this on the diff between 0.12 to 0.13, but I don't know enough about the codebase to know what would make sense. 😄 If there's nothing that sticks out to you, I can maybe try to bisect/cherry-pick between 0.12 and .013, build from source, and see if I can find something? |
Seeing the same.. just following the simplest example from the website in our codebase makes it hang for me:
with
{
"$schema": "./node_modules/oxlint/configuration_schema.json",
"plugins": ["import", "typescript", "unicorn"],
"env": {
"browser": true
},
"globals": {
"foo": "readonly"
},
"settings": {},
"rules": {
"eqeqeq": "warn",
"import/no-cycle": "error"
},
"overrides": [
{
"files": ["*.test.ts", "*.spec.ts"],
"rules": {
"@typescript-eslint/no-explicit-any": "off"
}
}
]
} As soon as I remove the 'import' plugin it doesn't hang |
Checking here, we have a path in {
"compilerOptions": {
"paths": {
"BAR/*": ["*"]
},
}
}
{
"compilerOptions": {
"paths": {
"BAR/src/*": ["./src/*"]
},
}
}
edit: a simple change from |
i can repro this with https://github.com/jsx-eslint/eslint-plugin-jsx-a11y |
I can confirm that's in our repository, so that could be my case. |
sorry meant if i clone that repo and run it i can repro this hanging |
it appears to hang here. oxc/crates/oxc_linter/src/service/module_cache.rs Lines 61 to 65 in c00f669
|
bisecting now,
|
ok, so it broke in 878189c hmm i don't know enough about this to do a fix. @Boshen any ideas? the reason this is happening is because we early return here: if there're any parser errors OR the lang was flow oxc/crates/oxc_linter/src/service/runtime.rs Lines 202 to 206 in 878189c
however we've already inserted the record here:
as we early returned, we never hit this line: oxc/crates/oxc_linter/src/service/runtime.rs Line 220 in 878189c
i guess we could insert an empty module record if we failed to parse/the lang is flow? |
Running for me now! Thanks! |
Was hoping to try out the fix for #7123 but adding
--import-plugin
is causing Oxlint to hang. I see output for many found errors but then it halts suddenly.I'm trying to eventually run
oxlint -A all -D no-cycle --import-plugin
so trying to see what works and what doesn't:Working:
oxlint
, exits as expectedoxlint -A all
, exits as expectedoxlint -D no-cycle
, exits as expectedNot working:
oxlint --import-plugin
, produces output for many errors, then haltsoxlint -A all --import-plugin
, no output, appears to hang (makes sense)oxlint -D no-cycle --import-plugin
, produces output for many errors, then haltsThis appears to be a regression specifically in 0.13.0. 0.12.0 is working as expected in all cases.
The text was updated successfully, but these errors were encountered: