Not working. Too many features and steps?

[josemigallas]

👓 What did you see?

I just tried the extension for the first time and it doesn't seem to work properly. When reloading the window, the first .feature files has syntax highlight but all steps are marked as undefined:

However, opening a second file doesn't:

The Cucumber Language Server output is:

[Info  - 8:38:54 AM] Initializing connection from Visual Studio Code 1.73.1
[Info  - 8:38:54 AM] Root uri    : file:///Users/jgallaso/projects/3scale/porta
[Info  - 8:38:54 AM] Current dir : /
[Info  - 8:38:54 AM] Registering request handler for workspace/didChangeConfiguration failed.
[Info  - 8:38:54 AM] Client does not support client/registerCapability. This is OK.
[Info  - 8:38:54 AM] Cucumber Language Server 1.1.1 initialized
[Info  - 8:38:54 AM] Scheduling reindexing in 3000 ms
[Info  - 8:38:54 AM] Scheduling reindexing in 3000 ms
[Info  - 8:38:54 AM] Reindexing file:///Users/jgallaso/projects/3scale/porta
[Info  - 8:38:56 AM] * Found 280 feature file(s) in ["src/test/**/*.feature","features/**/*.feature","tests/**/*.feature","*specs*/**/.feature"]
[Info  - 8:38:56 AM] * Found 8292 steps in those feature files
[Info  - 8:38:57 AM] Reindexing file:///Users/jgallaso/projects/3scale/porta

I suspected it would simply take some time but I've been waiting for a while and nothing changes.

✅ What did you expect to see?

I expected it working normally.

📦 Which tool/library version are you using?

macOS 13.0.1 (with m1 chip)
Visual Studio Code 1.73.1
ruby 2.6.10p210 (2022-04-12 revision 67958) [arm64-darwin21]
cucumber 7.0.0
cucumber/vscode 1.5.1

🔬 How could we reproduce it?

In order to reproduce, I guess you'd need to clone our repo (https://github.com/3scale/porta.git) since it has the big amount of features and steps. I know, it sucks, but I don't have an easier way to reproduce this at the moment.

---

This text was originally generated from a template, then edited by hand. You can modify the template here.

[aslakhellesoy]

Wow 8292 is a lot of steps! With that many steps it's possible that at least one of the following is happening:

• The language server is running out of memory
• Indexing is too slow and would need minutes or hours to complete

I think the first step is to add some more progress output to the indexing, if possible. I'm moving this over to language-service, where the indexing logic is implemented.

[aslakhellesoy]

Looking at the logs again, it looks like reindexing worked the first time, and only took a couple of seconds. It's the second time it doesn't complete. That rules out the slowness hypothesis. It could still run out of memory though.