Caching the hard drive for third-party libraries

ging-dev

JakubMisek ah yes, my fault. Seems like hover of final class may not show

ging-dev

Found a new bug in lastest pre-release v1.38.13753: https://github.com/ging-dev/devsense-lsp-reproduce/commit/9ab595ddd9824d1d5e4c5ebfd0efc61ae4f33b8a

JakubMisek

ging-dev thank you for the test case.

This is probably a corrupted local cache (%localappdata%/DEVSENSE/packages-cache).

Please try deleting it (or just the affected packages from the cache) and let the tools reindex the /vendor/ folder.

ging-dev

JakubMisek Thanks!, I cleared the cache and it worked, but I still can't seem to hover over Symfony\Component\Security\Http\Attribute\IsGranted to see the constructor parameter.

Lastest version:

Old version:

JakubMisek

ging-dev thanks, I can repro the issue easily. Will be fixed.

JakubMisek

Preparing pre-release with the fix, thanks!

ging-dev

JakubMisek Thank for quick fix!
If we accidentally press Go to definition on keyword true or false, we will receive this message:

Problems is disabled in pre-release or is it a bug? it only work the first time I open vscode

JakubMisek

ging-dev Thanks, this has been fixed in the latest pre-release, and the next updates will avoid generating $Metadata$ file at all.

ging-dev

JakubMisek

Source action seems to lose the ability to convert FQCN to Import (use).
Error diagnosis seems to stop working for me, I only get error diagnosis in case of incorrect syntax, cases of calling non-existent methods are not reported.

JakubMisek

ging-dev It is expected inside /vendor/ files or files outside the workspace. Does it happen in your user files as well?

ging-dev

JakubMisek yes it happens in user files, official release it still works, until i tested on pre-release

JakubMisek

ging-dev thanks! found bug in pre-release and fixing.

ging-dev

JakubMisek Thanks, the release is working fine for me!
There are a few small things that I think can be improved in the upcoming releases:

When indexing a large project for the first time, the amount of RAM that the LSP uses seems to be much higher than in subsequent operations.
If using the Go to Definition feature multiple times on items within the /vendor/ directory, it appears that the LSP will index them, causing an increase in RAM usage (not sure).

JakubMisek

ging-dev Thank you for all the feedback @ging-dev.

The latest 1.38 version seems to be stable. To decrease RAM after indexing large /vendor/ folder, I would recommend (for now) closing and re-opening the workspace, although, we'll be working on it in the upcoming updates.

For comparison, plain new Laravel 10 consumes about 69 - 80 MB of RAM, latest Drupal is about 480MB. We'll be working on it constantly.

« Previous Page