-
Notifications
You must be signed in to change notification settings - Fork 44
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
Range exceptioning on bad inputs #150
Comments
This issue is also being tracked on Linear. We use Linear to manage our development process, but we keep the conversations on Github. LINEAR-ID: 6ff8371d-d1a0-4b34-82bf-bde8708d28be |
We are still seeing this in the sentry logs. @OmarTawfik raised the point this may be related to some errors returned from solc not having source locations (i.e. |
I have a suspicion it is related to checks like these: hardhat-vscode/server/src/services/validation/DiagnosticConverter.ts Lines 76 to 82 in 9cfb24b
hardhat-vscode/server/src/compilerDiagnostics/conversions/constrainByRegex.ts Lines 10 to 12 in 9cfb24b
I wonder if we should treat such locations as |
@kanej This error is from 0.5.4 and earlier. Since then I've changed the import path completions logic and we don't have occurrences of this error on newer versions. Should I close the issue ? |
Sentry is confusing on these sorts of thing. It doesn't necessarily merge new instances with the old version. The |
If the import completion is triggered by deleting a quote on an existing import and readding it then, the position is the start of the import but we delete the entire length of the import line which creates a negative position triggering the bug. Instead, we short circuit. If the import is already the suggestion we don't suggest it again. Fixes #150.
Sentry Issue: VSCODE-EXTENSION-1QN
We are doing a range conversion that is throwing on bad inputs.
The text was updated successfully, but these errors were encountered: