-
Notifications
You must be signed in to change notification settings - Fork 338
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
Exception on a "strange" source jar #1304
Comments
I have seen the same exception with a couple of |
Thanks for reporting! The one @Arthurm1 is connected to This is just a warning. We might need to change that to debug, since it is quite misleading. |
There's not much we can do on our side, apart from maybe handling the error in a less scary way. I've reported the issue in danfickle/openhtmltopdf#428 |
Thank you for reporting! Metals should probably not log errors in cases like this. The error shouldn’t cause problems for metals functionality |
Thanks for the info - I'll close as it's a valid warning. |
Reopening since I think Metals should not report such noisy logs for warnings like this. |
I reopened it since we might be able to skip the wrong directory when listing everything recursively. Let's investigate this one. |
I haven't seen issues with this recently and just checked again to see how much effort it would be to skip the directory and it seems that would be a bit more complex, so let's leave it a is. |
I get an exception when importing a build in VSCode
To Reproduce
Click for Exception
The jar structure is strange - it has a directory that has no name but 7zip can drill down into it and extract the files.
No other source jars show errors.
Installation:
The text was updated successfully, but these errors were encountered: