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.

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

indexing conflict with rust-intellij plugin #317

Open
mattsse opened this issue Jul 23, 2022 · 7 comments
Open

indexing conflict with rust-intellij plugin #317

mattsse opened this issue Jul 23, 2022 · 7 comments

Comments

@mattsse
Copy link

mattsse commented Jul 23, 2022

as discovered here

intellij-rust/intellij-rust#9008

Having a rust dependency that has solidity fixtures can result in a hung indexer.

this happens with the https://github.com/hyperledger-labs/solang project

disabling the solidity plugin resolved the issue so perhaps the problem is somewhere in this plugin's indexer?

this also happens with plugin built from master

@moh-eulith
Copy link

This issue is easily reproducible. Any chance we could get a fix?

@mattsse
Copy link
Author

mattsse commented Aug 18, 2022

this hasn't happened in a while, at least for me, perhaps this just doesn't happen anymore with a newer solang-parser release.
but when it did, I was able to work around this by deleting all sol files from External Libraries/solang-parser/... in the project view

@moh-eulith
Copy link

moh-eulith commented Aug 18, 2022

It's happening with solang-parser 0.1.17 (latest) for me. I'll try deleting those files. Thanks for the hint. Right now, I have to alternately enable/disable either rust or solidity.

@SerCeMan
Copy link
Member

SerCeMan commented Sep 3, 2022

Hey, @moh-eulith! Can you still reproduce the issue with the latest IJ solidity plugin (2.3.10)?

@moh-eulith
Copy link

@SerCeMan Yes, with both the latest Rust (0.4.177.4844-222) and Solidity (2.3.10) plugins, this problem still occurs. The workaround (deleting the testdata folder under the External Libraries/solang-parser 0.1.17/solang-parser-0.1.17 also avoids the issue by removing the offending file, which is apparently not really needed).

@rafales
Copy link

rafales commented Feb 7, 2023

Still occurs.

@lightsing
Copy link

still

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants