You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DH-20578: Adds Groovy support for remote file source features in VS Code
extension. The supporting plugin work has not fully landed yet mostly
waiting on tests, but I don't think that should block this PR:
**Related Pending PRs**
Changes for these are deployed to `bmingles-remote-file-source2` BHS
- deephaven/deephaven-core#7451
- deephaven-ent/iris#3878
- TBD: PR to integrate Core changes into gplus
## Testing
- Test on a grizzly or gplus server without the plugin installed. Verify
that we can still run python and groovy scripts without remote file
sourcing. This is just a regression test.
- `bmingles-remote-file-source2` has Groovy and Python remote plugins
installed, so full feature set can be tested there
### Setup
- Start `bmingles-remote-file-source2` vm if not already running
- Clone this test repo
`git@github.com:bmingles/deephaven-controller-script-test`
- Checkout the `local` git branch (the `main` branch is configured as a
controller source on `bmingles-remote-file-source2`).
### Local override tests
- Connect to `bmingles-remote-file-source2` server in VS Code
- Open and run `src/main/groovy/docs-sample.groovy` against the BHS
- Should see STDOUT entries in OUTPUT -> Deephaven panel with `"Server"`
prefix e.g.
```
12:16:14.829 STDOUT Server: Notebook Level Var
12:16:14.830 STDOUT Server: Notebook Level Var
12:16:14.830 STDOUT Server: Top Level Var
12:16:14.830 STDOUT Server: Top Level Var
...
```
- Cells in the `testTable` should also include the `"Server"` prefix
- Add `src/main/groovy/test` folder as a Groovy remote file source
- Run the script again. Should see `"Local"` prefix e.g.
```
12:21:12.336 STDOUT Local: Notebook Level Var
12:21:12.336 STDOUT Local: Notebook Level Var
12:21:12.337 STDOUT Local: Top Level Var
12:21:12.337 STDOUT Local: Top Level Var
...
```
- Cells in the `testTable` should also include the `"Local"` prefix
- Remove the `src/main/groovy/test` as a remote file source
- Run the script again. STDOUT and table cells should all go back to the
`"Server"` prefixes
### Tree Selection Behavior
There was a bug fixed in this PR that impacts how partial unmarking
works in the Remote file source tree view.
- Navigate to Deephaven activity bar tab (left sidebar)
- Expand Groovy workspace tree until you get to
`src/main/groovy/nested/ws1`
- Add `ws1` folder as remote source with the `+` button
- Should see ws1 and all of its children turn green
- Hover over `ws1/sub1` subfolder and click the `-` sign to remove it
- Result should be that `ws1/sub2` is now the marked folder. `ws1/sub1`
and `ws1/file1.groovy` should both be unmarked
Copy file name to clipboardExpand all lines: skills/deephaven-vscode-using/SKILL.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,12 +76,14 @@ Community servers always support panel URLs. Enterprise servers require Grizzly+
76
76
77
77
### Remote File Sources
78
78
79
-
Enable server to fetch source files during execution:
79
+
Configure which workspace folders the server fetches source files from during execution:
80
80
81
81
- Add folder URIs as remote sources (`addRemoteFileSources`)
82
82
- List current sources (`listRemoteFileSources`)
83
83
- Remove sources when done (`removeRemoteFileSources`)
84
84
85
+
If an import error occurs, follow the hint in the tool response — it will specify how to resolve it.
86
+
85
87
### Troubleshooting
86
88
87
89
**MCP Server Not Running:**
@@ -114,6 +116,10 @@ Server connections are managed through MCP tools. Use `listConnections`, `listSe
114
116
115
117
All MCP tools are available when the MCP server is enabled via `deephaven.mcp.enabled` setting. If tools aren't available, ensure MCP is enabled (see Troubleshooting).
116
118
119
+
### Tool Response Hints
120
+
121
+
Tool responses may include hints that guide next steps. Consider them before deciding how to proceed.
0 commit comments