Language Server - High CPU Utilization in GitLab Development Kit - Injected Context

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Reported by @mcelicalderonG during internal testing:

Mario Celi
:ferris_wheel:  Oct 17th at 4:10 PM
@Angelo Rivera
 I think I'm still experiencing some high cpu usage related to the GitLab plugin
This is what I'm seeing in the logs for Gitlab Language Server

2024-10-17T15:10:09:965 [debug]: DirectoryWalker: found 0 paths, took 138263ms
2024-10-17T15:10:10:011 [debug]: [RepositoryService] File file:///Users/mcelicalderon/gitlab/main_install/gitlab/db/schema_migrations/20241001122042 removed from repository file:///Users/mcelicalderon/gitlab/main_install/gitlab
2024-10-17T15:10:10:011 [debug]: DirectoryWalker: found 0 paths, took 138309ms
2024-10-17T15:10:10:056 [debug]: [RepositoryService] File file:///Users/mcelicalderon/gitlab/main_install/gitlab/db/schema_migrations/20241001122043 removed from repository file:///Users/mcelicalderon/gitlab/main_install/gitlab
2024-10-17T15:10:10:056 [debug]: DirectoryWalker: found 0 paths, took 138354ms
It just continues to output that

Now the output stopped, but I still have a plugin process of 100% cpu usage
4:14
mcelicalderon    22815  96.7  1.8 1596781440 616736   ??  R     2:50PM  10:15.15 /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper (Plugin).app/Contents/MacOS/Code Helper (Plugin) /Users/mcelicalderon/.vscode/extensions/gitlab.gitlab-workflow-5.15.0/assets/language-server/node/main-bundle.js --use-source-maps --stdio --clientProcessId=22068

During sync testing with @mcelicalderonG, we found this bug is reproducible with the following steps:

• have the feature enabled with duo_additional_context and language server debug: true
• open gitlab development kit folder in VSCode
• run gdk update, which will trigger a large branch change
• See the process hang/remain at high CPU usage during schema_migrations path changes in the RepositoryService, indicated by DirectoryWalker: found 0 paths, took 138354ms