Skip to content

Feedback

Use the vscode-kdb GitHub issue tracker for bugs, capability requests, and documentation corrections.

Useful report details

  • KX for VS Code version or commit.
  • VS Code version and operating system.
  • kdb+/q version.
  • Whether the target is loopback, private network, or a separately managed tunnel.
  • Endpoint host category and port, with sensitive infrastructure generalized when needed.
  • Which command and execution mode failed: current line, single-line selection, multiline selection, or script.
  • For notebooks: selected controller, cell language, and whether execution used Run q Cell (KX), the explicitly enabled optional KX controller's native Run, or Python %%q. Include the globally starred active profile/namespace for extension Direct IPC, whether that profile was edited, or Python/IPython plus kx-notebook distribution and kx_notebook import versions for the companion. Also include presentation setting, saved-output row/byte limits and saved/total counts, whether an extension direct live record was still available, and whether the issue occurs during Run, live rendering, reopen, panel handoff, or static HTML/PDF export.
  • Result shape and approximate rows/columns for viewer, chart, copy/export, or performance problems.
  • Minimal reproduction steps and expected/actual behavior.
  • Relevant View > Output > KX records after reviewing them for environment-sensitive metadata.
  • Whether vscode-kdb.performance.trace was enabled.

Never include passwords, authentication strings, SecretStorage contents, tokenized local-data-server URLs, proprietary result values, or production query text. Diagnostics are designed to omit credentials and query values, but review copied output before posting it publicly.

For charting reports, include the chart type, X/Y or OHLC selection, whether grouping was enabled, which legend series were hidden, the navigator/zoom range, the refresh that changed state, and the displayed eligible-row/rendered-item status and warnings. For notebook charts, also distinguish the emitted persisted specification from renderer-only session changes. For cancellation reports, distinguish local panel cancellation from explicit connection disconnect.