chroe(vscode): Refresh vscode integration lockfile

[amanape]

• This change is worth documenting at https://docs.all-hands.dev/
• Include this change in the Release Notes. If checked, you must provide an end-user friendly description for your change below

End-user friendly description of the problem this fixes or functionality this introduces.
Patches critical vulnerability

---

Summarize what the PR does, explaining any non-trivial design decisions.

---

Link of any specific issues this addresses:

---

To run this PR locally, use the following command:

GUI with Docker:

docker run -it --rm   -p 3000:3000   -v /var/run/docker.sock:/var/run/docker.sock   --add-host host.docker.internal:host-gateway   -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:026aed6-nikolaik   --name openhands-app-026aed6   docker.all-hands.dev/all-hands-ai/openhands:026aed6

CLI with uvx:

uvx --python 3.12 --from git+https://github.com/All-Hands-AI/OpenHands@chore/refresh-vscode-lockfile openhands

[enyst]

Oh, thank you!

Hmm, will need to think of something to keep it close to FE 🤔

[openhands-ai]

Looks like there are a few issues preventing this PR from being merged!

• GitHub Actions are failing:
  • VSCode Extension CI

If you'd like me to help, just leave a comment, like

@OpenHands please fix the failing actions on PR #9965

Feel free to include any additional details that might help me get this PR into a better state.

_{^{You can manage your notification settings}}

[amanape]

@OpenHands please investigate and fix the failing actions on PR #9965

[openhands-ai]

I'm on it! amanape can track my progress at all-hands.dev

[openhands-ai]

Perfect! Let me now check if the request has been completely addressed:

Request Analysis Checklist:

✅ 1. Investigated failing actions on PR #9965

• Identified that the "VSCode Extension CI" workflow was failing
• Found the specific failing step: "Validate .vsix file"

✅ 2. Root cause analysis

• Discovered that the lockfile refresh updated the glob package from older versions to v11.0.3
• The newer glob version has a different API that's incompatible with the old callback-based usage

✅ 3. Fixed the failing action

• Updated openhands/integrations/vscode/src/test/suite/index.ts to use the new glob v9+ API
• Changed from glob = require("glob") to import { glob } from "glob"
• Converted from callback-based pattern to modern async/await pattern
• Fixed ESLint issues (no-var-requires and return-await)

✅ 4. Verified the fix

• Successfully built the VSCode extension locally
• Confirmed the .vsix file is generated and valid
• Passed all linting and type checking
• Committed and pushed the fix to the PR branch

✅ 5. Changes are concise

• Only modified the necessary file to fix the compatibility issue
• No extraneous changes were made
• The fix is minimal and targeted

Final Summary

I successfully investigated and fixed the failing actions on PR #9965. The issue was in the VSCode Extension CI workflow, specifically in the "Validate .vsix file" step.

Root Cause: The PR refreshed the VSCode integration lockfile, which updated the glob package from older versions to v11.0.3. The newer glob version has a different API that's incompatible with the old callback-based usage in the test suite.

Solution: I updated openhands/integrations/vscode/src/test/suite/index.ts to:

• Use the new glob v9+ import syntax: import { glob } from "glob"
• Convert from callback-based pattern to modern async/await pattern
• Fix ESLint issues related to the changes

Verification: The fix has been tested locally - the VSCode extension now builds successfully, generates a valid .vsix file, and passes all linting checks. The changes have been committed and pushed to the PR branch, triggering new workflow runs that should now pass.

The failing action has been resolved, and the PR should now have all checks passing.

[enyst]

A quick test, just that it installs and still does one of the commands, e.g. a menu command with selected text, will be great!

[Abubakar-01]

PR Review
Before (Main Branch): VSCode extension uses legacy glob callback-based API (glob = require("glob")) with glob v11.0.0 package, and all tests pass successfully (16/16).

After (PR Branch): Code is updated to use modern ES6 import syntax (import { glob } from "glob") and async/await pattern, but encounters TypeScript compilation errors despite using the correct glob v11 API syntax.

TypeScript Errors:

src/test/suite/index.ts:18:49 - error TS2353: Object literal may only specify known properties, and 'cwd' does not exist in type '(err: Error | null, matches: string[]) => void'.

src/test/suite/index.ts:21:11 - error TS2339: Property 'forEach' does not exist on type 'IGlob'.

Conclusion:
The PR uses correct glob v11 API syntax but TypeScript fails to resolve the proper type definitions, causing compilation errors due to import resolution issues.

[enyst]

I think I saw in the lockfile that it uses some sub-packages like glob/types from 8.x version, and glob from 11.x version. That might explain it!

I’m on an iPad in the forest (literally), maybe OH can help us here until I get back? 😅

Changes made

[github-actions]

🔧 VSCode Extension Built Successfully!

The VSCode extension has been built and is ready for testing.

📦 Download: openhands-vscode-0.0.1.vsix (23 KB)

🚀 To install:

1. Download the artifact from the workflow run above
2. In VSCode: Ctrl+Shift+P → "Extensions: Install from VSIX..."
3. Select the downloaded .vsix file

✅ Tested with: Node.js 22
🔍 Validation: File structure and integrity verified

---

Built from commit 3335792

[enyst]

@Abubakar-01 Thank you! I now downloaded the .vsix, cleaned up the older install, installed from vsix, then tried the context menu "OpenHands -> start with selected text" and "with file" and it worked.

If it doesn't, could you please tell what exactly you do that fails?

[Abubakar-01]

@enyst Just tried again, It is working for me aswell!

[enyst]

Thank you!