What's going with 1.6 version just released? Ruby LSP not logger working

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

On macos, after updated to the latest version just prompted, “Ruby LSP” plugin couldn’t work any longer, maybe it’s related to security issue:

2025-09-10 15:40:27.715 [info] (engine) Running command: `/opt/homebrew/bin/mise x -- ruby -EUTF-8:UTF-8 '/Users/xxxx/.cursor/extensions/shopify.ruby-lsp-0.9.32-universal/activation.rb'` in /xxxx using shell: /opt/homebrew/bin/zsh

The plugin output stopped at the above command.

I reverted to 1.5 version, ruby lsp will work again, no problem with vscode.

Updated to nightly version, which is 1.6 version, the issue will be raised.

Automatic Ruby environment activation with mise failed: Cannot read properties of null (reading '1')

Steps to Reproduce

Updated to nightly version of cursor, with ruby lsp plugin, will raise error about ruby cannot be detected automatically.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.6.3
VSCode Version: 1.99.3
Commit: 6ff61021bde05fe311c784a7d29c9320976128c0
Date: 2025-09-09T22:59:10.623Z (10 hrs ago)
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like

Same here

Hi @pzgz and @Robert_Chang thank you for the report.

Yes we are launching 1.6 in stages. I will forward your report to the team.

cc @ravirahman

1 Like

Hi @pzgz and @Robert_Chang, we are working on a hotfix for this bug. Thank you for reporting it. In the meanitme, please downgrade to Cursor 1.5.

2 Likes

If it helps: exec[promisify.custom] is undefined, this breaks the ruby-lsp activation script, because we don’t get the expected result { stdout, stderr } = await exec()

1 Like

Confirmed fixed in Version: 1.6.6, thanks